It is trying to use an old backup mechanism , the way to read the error
(not that you should have to understand this, it's terrible) is
Could not load a ruby extension named "file.rb" for the "file_bucket_file"
setting.
The shortest fix is to set "File { backup => false }" in your site.pp.
--
You're correct John - Puppet 4 masters using Puppet Server will work with
Puppet 3 agents. If the catalog compiles (Henrik's point), the
agent/master comms will be fine.
Note the same is not true for Apache/Passenger based Puppet 4 setups - the
URL rewriting that enables the compatibility is o
Vlastimil - I'm forwarding this message to the puppet-users list instead of
puppet-announce.
--eric0
> From: vlastimil.ho...@gmail.com
> Subject: Re: Bolt 1.8.0 now available
> Date: January 4, 2019 at 3:46:31 AM PST
> To: Puppet Announce
>
>
> Hello,
>
> On Friday, January 4, 2019 at 12:01:
Andy, did you get this fixed?
--eric0
On Friday, November 16, 2018 at 9:02:02 AM UTC-8, Andy Hall wrote:
>
> Hmm perhaps I should RTFM :
> https://puppet.com/docs/puppetdb/6.0/maintain_and_tune.html#redo-ssl-setup-after-changing-certificates
>
> On Friday, 16 November 2018 16:49:20 UTC, Andy Hal
Hi Darragh, the fact that the error message contains a '400' error suggests
the problem happens on the server when it receives the report.
My first guess given that error message is also that there's a mix of
versions installed, but it's weird that it only happens on some reports.
Maybe there
Sorry Rafael, I don't understand what you're asking. Can you share the
puppet code that you are trying to use, and the error message you get?
--eric0
On Wednesday, November 28, 2018 at 5:54:34 AM UTC-8, Rafael Tomelin wrote:
>
> Hi,
>
> How configure path in puppet.agent.
>
> I need path = sourc
Hi Soham, I would suggest you start with a single server that contains both
the CA and compile master functionality.
That way you can bootstrap it in a very simple way, using the instructions
for the new intermediate CA setup in Puppet 6. Once that is working, it is
much easier to move to a spl
You could put that same yaml or json in /etc/puppetlabs/facter/facts.d and
the whole data structure will be available under $facts ...
--eric0
On Monday, November 26, 2018 at 11:14:27 AM UTC-8, Henrik Lindberg wrote:
>
> On 2018-11-23 03:27, Abhijeet Rastogi wrote:
> > Hi everyone,
> >
> >
>
Enterprise. If
you have any questions about upgrading, be sure to get in touch with Puppet
Support.
Eric Sorenson - e...@puppet.com
director of product
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop
.
As always, we want to hear about your experiences with Puppet Enterprise. If
you have any questions about upgrading, be sure to get in touch with Puppet
Support.
Eric Sorenson - e...@puppet.com
director of product
--
You received this message because you are subscribed to the Google Groups
-9156) and improvements to
the handling of Sensitive data (PUP-7580).
Full release notes for the release are available here:
https://puppet.com/docs/puppet/6.0/release_notes.html#puppet-603
Eric Sorenson - e...@puppet.com <mailto:eric.soren...@puppet.com>
director of product
--
You recei
The latest point release of the Puppet Platform 5 series is now available.
This is a backwards-compatible bugfix release that contains several important
fixes for open source and PE users (this release will roll into the next PE
2018.1.x LTS point release, slated for Nov 6).
For the full list
Thanks for reporting this duritong - I wanted to follow up to say that this
was fixed in 6.0.2 (indeed this was the reason we shipped 6.0.2 after 1
day:) )
On Wednesday, October 3, 2018 at 1:30:22 AM UTC-7, Peter Meier wrote:
>
> Hi All,
>
> > We're happy to announce the release of Puppet Platf
On Jul 17, 2018, at 2:26 AM, Martin Alfke wrote:
>
>> On 17. Jul 2018, at 01:40, Eric Sorenson > <mailto:e...@puppet.com>> wrote:
>>
>> So my question is -
>> - do you current use/rely on 'gem install puppet' for your workflows? If so,
&g
Another effort that's underway but not yet complete is the extraction of
non-core types/providers into modules. This addresses some long-standing
requests to, for example, be able to change the nagios types and OS-specific
resources without needing to get a full agent release out. The extracted
backwards incompatibilities or
> deprecations?
>
> Best
> Al
>
> On Monday, April 23, 2018 at 11:44:32 PM UTC+2, Eric Sorenson wrote:
>>
>> Hi all, we've started landing changes for what will become Puppet
>> Platform 6. Here's the News You Can Use relat
Hi all, we've started landing changes for what will become Puppet Platform 6.
Here's the News You Can Use relating to the release.
Scope and Timeline
We expect to release it in the fall, and the major features of the release are
currently scoped to be:
- improved secret and ephemeral data handl
Yep, this was an error in the build/ship process - we're scrubbing them out
now. Sorry for the confusion.
--eric0
On Wednesday, April 18, 2018 at 12:25:23 AM UTC-7, Brent wrote:
>
> Just a question
>
> Shouldn't the puppet 5 packages not be in
> http://apt.puppetlabs.com/pool/stretch/PC1/p/pupp
ot sure how this would be an
> improvement over just enabling autosign. Private keys should remain
> private to a node and should never be transmitted over the network if
> possible.
>
> On Wednesday, March 28, 2018 at 3:10:35 PM UTC-4, Eric Sorenson wrote:
>>
>> Is anybody out
Is anybody out there pre-generating certificates for your agents? I've
heard whispered tales of some folks doing this but we're starting work on
improving the CA / signing / revocation workflow and it'd be great to talk
to somebody directly. The workflow would be using 'puppet cert generate' on
I made a quick blog post about it here:
https://puppet.com/blog/2018-puppet-user-survey
And here's a direct link to the survey:
https://www.surveygizmo.com/s3/4227485/puppet-users
--eric0
Eric Sorenson - e...@puppet.com <mailto:eric.soren...@puppet.com>
director of product, ecosyst
Close, the PE2016.4 LTS uses Puppet 4 and is supported through October
2018.
--eric0
On Monday, February 12, 2018 at 9:15:20 AM UTC-8, R.I. Pienaar wrote:
>
>
>
> On Mon, 12 Feb 2018, at 17:43, Sven vd wrote:
> > Hi,
> >
> > Currently our infrastructure and code is written with and run by pu
Hi Jack, for puppet enterprise there's a built-in workflow for assigning
classes to nodes - the phrase you're looking for is called "node
classification" in puppet-speak. here's the relevant
doc:
https://puppet.com/docs/pe/2017.3/managing_nodes/grouping_and_classifying_nodes.html
hope this he
previously Bolt would did
not securely verify keys for hosts it had not connected to before.
Complete release notes and more info about bolt:
https://puppet.com/docs/bolt/0.x/bolt_overview.html
--eric0
Eric Sorenson - e...@puppet.com
director of product, ecosystem and platform
--
You receive
slack.puppet.com <http://slack.puppet.com/> #puppet-tasks.
Eric Sorenson - e...@puppet.com <mailto:eric.soren...@puppet.com>
director of product, ecosystem and platform
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscri
erver/latest/release_notes.html
Eric Sorenson - e...@puppet.com
director of product, ecosystem and platform
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an e
stall puppet server, follow these instructions:
https://docs.puppet.com/puppetserver/2.8/install_from_packages.html
Eric Sorenson - e...@puppet.com <mailto:eric.soren...@puppet.com>
director of product, ecosystem and platform
--
You received this message because you are subscribed to the Go
Hi Dominic, thanks for tracking this down and documenting it so thoroughly.
Some responses inline:
On Tuesday, August 1, 2017 at 9:56:28 PM UTC-7, Dominic Scheirlinck wrote:
>
> Thought I'd leave a note about an issue I ran into when upgrading to
> Puppet 5.0.1, in case someone else is wrestling
The best way to do this is to use puppetdb, which you can then query from
manifests using the puppetdb_query() function.
Your query would look like (untested but i think this is right...)
$nodes_array = puppetdb_query('inventory[certname] { resources { type =
"OurSystem" } }')
(You may see ref
— extra special thanks to Josh Cooper for
shepherding this out the door. It has a special significance for me since it's
version five and (by total coincidence!) yesterday was my five year anniversary
at Puppet :) I think it's going to be a great release series.
Eric Sorenson - e...@pupp
tl;dr: There are new builds in the 'puppet5-nightly' repos. Please give them a
spin and let us know what you find!
Since we pushed the first builds of what will become the Puppet 5 Platform
packages into the repos, a *lot* has been going on. We're nearing code-complete
on the release and it see
The benefit at the end of all of this will be that we will be able to provide
much better response time for new issues as they come in.
Eric Sorenson - e...@puppet.com
director of product, ecosystem and platform
--
You received this message because you are subscribed to the Google Groups
"P
Hi Peter, this is a known problem that is tracked
in https://tickets.puppetlabs.com/browse/PUP-6739
--eric0
On Friday, February 17, 2017 at 11:53:50 AM UTC-8, Peter K wrote:
>
> I fixed my site.pp and that got my hiera lookups working...but I still
> dont' understand the puppet config results.
That's great to hear François, thank you for testing the patch! Our plan at
this point is to accumulate a couple more fixes and ship a new build by
Tuesday 21 Feb -
I don't want to generate a new build containing only the fix in PUP-7215
because
(a) there is QA work underway on the current rel
Hey, it looks like everyone found this, but I wanted to add that we updated
this document with the hiera.yaml v5 format late last week, so if you were
looking for it outside of the google doc, it's up and running.
https://docs.puppet.com/puppet/4.9/lookup_quick.html#there-are-two-hierayaml-forma
rade Puppet Agent, follow the getting started directions:
http://docs.puppetlabs.com/puppet/latest/reference/index.html
For information on upcoming platform end-of-life (EOL) for Puppet Agent, please
see our Platform Support Lifecycle page:
https://puppet.com/content/platform-support-lifecycle
Eric
On Monday, January 9, 2017 at 6:56:34 AM UTC-8, John Gelnaw wrote:
>
> On Sunday, January 8, 2017 at 2:31:33 PM UTC-5, Rob Nelson wrote:
>>
>> There are a lot of very valid issues and concerns you bring up here. I do
>> want to start by saying, however, that puppet 4 is more than 6 months old -
Hi Joe, It's an agent-side setting (the facts are "stringified" on the
agent before the server ever sees them) so it needs to happen on the
agents. But if you're not currently managing your config file with puppet
itself you can use a module like
this: https://forge.puppet.com/cjtoolseram/puppe
Hi Thomas, have you tried the `puppet generate type` workflow described on
that doc to avoid the problems with environment bleed-through? You said you
failed w/the elasticsearch module and I'm wondering if that is because the
`generate` stuff is not working, or whether there's another part of th
; sign up at https://slack.puppet.com/ if you're not already
logged in.
Thanks and happy upgrading!
--eric0
Eric Sorenson - eric.soren...@puppet.com - freenode #puppet: eric0
puppet ecosystem product manager
--
You received this message because you are subscribed to the Google Groups
&qu
Hi Iván - I think there are a couple of approaches that could work for you.
1 - you could continue to provision as you do today, but include a step in
the shut-down that cleans a certificate. It is possible to add a rule to
the auth.conf file that permits access to puppet's HTTPS endpoints which
Awesome, Ger! Your talks and blog posts are always great and the puppet
infra you recommend is very clean. Best wishes for your class.
--eric0
On Friday, July 1, 2016 at 3:42:18 AM UTC-7, Ger Apeldoorn wrote:
>
> Hi all!
>
> I see people struggle with their Puppet setups over and over again. It
This is not fully supported yet, but can work with a couple of caveats -
the question has come up a few times recently.
Can you please try my draft HOWTO documentation at this gist, and let me
know how it works for you? You can reply here or comment on the gist if
there are specific lines that
hat gem and the latest mainline C++-facter.
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this
Matt, I would like to understand this better and help you adopt Puppet into
your environment.
This is not a rhetorical question, but it might sound like one: Do you
rebuild your linux distribution from source RPMs? Because that is very
similar to what the AIO Puppet agent bundle is: a mini dist
Check out this WIP doc where I describe how to get intermediate certs
working. It *is* possible but there are a couple of caveats described in
the doc.
If anyone's motivated to try this out and let me know how it works for you
I'd be hugely appreciative. I got it to "works for me" level of read
e full release notes here:
https://docs.puppet.com/puppetserver/latest/release_notes.html
To install or upgrade puppet-agent, follow the getting started directions:
http://docs.puppetlabs.com/puppet/latest/reference/index.html
Eric Sorenson - eric.soren...@puppet.com - freenode #puppet: e
I'm CC'ing Jo Rhett directly here in case he doesn't come across this
organically --
The only place the puppet:/// syntax has ever been valid is in the 'source'
attribute for File resources; the epp function, like template(), is
expanded on the master during compilation and the contents are inc
On May 19, 2016, at 5:54 PM, Eric Sorenson mailto:eric.soren...@puppet.com>> wrote:
>
> * Puppet 4.5.0 - Also primarily a bugfix release, with improvements in the
> type system and a few hotly awaited fixes for systemd and the DNF package
> manager. The release notes men
e main puppet-agent note:
https://docs.puppet.com/puppet/4.5/reference/release_notes_agent.html
<https://docs.puppet.com/puppet/4.5/reference/release_notes_agent.html>
Special community shout-out to Matthew Gyurgyik (whose name I admit i
copy-pasted from JIRA) for working thr
Hi Chris, in addition to all the practical advice for moving through the
upgrade cycles that you have gotten already, I would suggest taking a step
back and analyzing your existing code-base to understand what the actual
business function of the existing code is for the nodes. You can spend a
t
Puppet needs certificates in order to work, but you can autosign any
incoming request without manual intervention using autosign:
https://docs.puppet.com/puppet/4.4/reference/ssl_autosign.html
--eric0
On Thursday, May 12, 2016 at 5:29:44 AM UTC-7, Mr Dandy wrote:
>
> Is it possible to configure
Hi Sinux, what version of puppet are you using? There was a bug in this
area but it was fixed quite a while ago, in Puppet 3.1.0:
https://projects.puppetlabs.com/issues/18161
Can you paste the output of `puppet -tv --debug 2>&1 | grep SRV`
it should have some lines like:
Debug: Searching for
On Friday, May 13, 2016 at 2:57:57 PM UTC-7, Dan Mahoney wrote:
>
> Hey there puppet-users deinzens.
>
> One of my puppet agents helpfully reminded me that my root CA cert is due
> to expire within a few months, and I'm wondering what the best way to go
> about rolling it over would be.
>
> A l
https://docs.puppet.com/puppetserver/2.3/release_notes.html#puppet-server-232
For more information on the Puppet Server including
installation and upgrade instructions, read this:
https://docs.puppet.com/puppetserver/2.3/index.html
Eric Sorenson - eric.soren...@puppet.com - freenode #puppet:
.com/puppet/3.8/reference/pre_install.html
Special community shout-out for this release goes to Clay Caviness for the
launchd bug report and pull request in PUP-6073. You rock, Clay!
Eric Sorenson - eric.soren...@puppet.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
-
or Vaughan wrote:
> Security releases are really all that's important to most compliance-focused
> orgs.
>
> Could that page link to the versions of each sub-component that is included?
>
> Thanks!
>
> Trevor
>
> On Tue, Mar 22, 2016 at 11:37 AM, Eric S
Sorry for the slow reply, we had some internal ducks to get in a row. The
enterprise support page now shows the current support dates for all the
recent series:
https://puppetlabs.com/misc/puppet-enterprise-lifecycle
As a practical matter we're going to provide open-source releases of
compone
I'm really excited to announce the arrival of new feature releases:
Puppet 4.4.0 and Puppet Server 2.3.0. The headline feature here is
Static Catalogs: file resources with 'puppet:///' source attributes
will now include the checksum of the file inside the catalog, rather
than requiring additional
The first and most significant chunk of the direct puppet work, namely a
production-ready version of "static catalogs" is going out in Puppet 4.4.0.
You can preview the documentation for it
here:
https://github.com/puppetlabs/puppet-docs/blob/master/source/puppet/4.4/reference/static_catalogs.m
to the PIP
package provider.
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop r
pet/latest/reference/release_notes_agent.html
To install or upgrade puppet-agent, follow the getting started directions:
http://docs.puppetlabs.com/puppet/latest/reference/index.html
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
-
gt;"ignore",
> :rest=>"site_files/puppet-test"
>
This message is on the agent, there should be a corresponding message in the
server logs -- can you include that if you still have trouble after fixing the
'codes' -> 'code' path in fileserver.co
It is not deprecated at all.
Can you please post your configuration (fileserver.conf, auth.conf, and the
puppet manifest which causes the error) along with the exact error messages?
--eric0
On Monday, January 11, 2016 at 1:57:34 AM UTC-8, kashif wrote:
>
> Hi
>
> Is serving files from custom mo
/puppetserver/1.1/install_from_packages.html
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this
t and individual
components here:
http://docs.puppetlabs.com/puppet/4.3/reference/about_agent.html
To install or upgrade puppet-agent, follow the getting started directions:
http://docs.puppetlabs.com/puppet/4.3/reference/index.html
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet:
puppet-agent and individual
components here:
http://docs.puppetlabs.com/puppet/4.3/reference/about_agent.html
To install or upgrade puppet-agent, follow the getting started directions:
http://docs.puppetlabs.com/puppet/4.3/reference/index.html
Eric Sorenson - eric.soren...@puppetlabs.com
/reference/release_notes.html#puppet-384
Here's the complete list of bugs fixed in the release:
https://tickets.puppetlabs.com/issues/?filter=15901
To install or upgrade puppet, follow the installation guide:
https://docs.puppetlabs.com/guides/install_puppet/pre_install.html
Eric Sor
the component release notes.
To install or upgrade puppet-agent, follow the getting started directions:
http://docs.puppetlabs.com/puppet/4.2/reference/index.html
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
/about_agent.html
The installation and upgrade instructions are linked from the main docs page:
https://docs.puppetlabs.com/puppet/4.2/reference/index.html
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
uppetserver to
generate your _host_ key on the CA, that key and the 'privatekeydir'
directory will have too-lenient permissions.
--eric0
On Tuesday, September 29, 2015 at 9:47:57 PM UTC-7, Eric Sorenson wrote:
>
> We've identified and are fixing a condition in puppet wher
rver which has the CA key
- as root, `chmod 660 $(puppet master --configprint cadir)/ca_key.pem`
A huge thank you/merci to Francois Lafont for reporting this issue.
For more details, see https://tickets.puppetlabs.com/browse/PUP-5274
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #pupp
changes)
You can find out more about the all-in-one puppet-agent package here:
https://docs.puppetlabs.com/puppet/4.2/reference/about_agent.html
The installation and upgrade instructions are linked from the main docs page:
https://docs.puppetlabs.com/puppet/4.2/reference/index.html
Eric Sorenson
On Fri, 26 Jun 2015, Vince Skahan wrote:
yup - appreciate the responselet me know if you want me to open a
ticket to get this into the next 3.8.x (via my work email).
Yep, that's definitely the way to go. https://support.puppetlabs.com/
Eric Sorenson - eric.soren...@puppetlab
n Wed, 24 Jun 2015, Eric Sorenson wrote:
There's a new All-in-One Puppet Agent release available! This release bundles
new versions of several component projects and is downloadable now through
the Puppet Collection 1 repository.
* Puppet 4.2 includes several features and bug fixes, and
MzeJ-4x-kkgYkUZg>
Thanks to Erik Dalén and James Ralston for raising this issue and testing
the fix.
--eric0
On Wednesday, June 24, 2015 at 7:23:28 PM UTC-7, Eric Sorenson wrote:
>
> There's a new All-in-One Puppet Agent release available! This release
> bundles
> new
ones you care about, plus enough value-add
features, scale improvements, and workflows from the product to make it
valuable to you.
>
> Confused in the PL approach toward support of their 'commercial' vs. 'open
> source' product lines.
>
>
Hope this helps. You
tories for Puppet related projects, here:
https://puppetlabs.com/blog/welcome-puppet-collections
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
us.
I really want to understand this, because it's a big deal. (My life goal at
this point is to get as many people as possible upgraded to Puppet 4, so
anything that gets in the way of that is a problem!) There's been a bunch of
different points in the thread, some of them about the number
p-thread, because some packaging
systems don't view numbers not part of the 'version' field to be an upgrade.)
Does that align more closely with the least-surprising thing, to you?
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
Hi Steve, thanks for tracking this down! The LDAP node terminus is a useful
but pretty cobwebby corner of Puppet (IIRC it predates the existence of the
External Node Classifier API which is what most sites are using now). So as
you found its docs do not get a lot of love and there are no accepta
he releases are available as individual files on http://rubygems.org (as gems)
and http://downloads.puppetlabs.com/ (as tarballs).
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
--
You received this message because you are su
The canonical way to do this is like this:
http://serverfault.com/questions/350230/how-can-i-have-puppet-only-set-password-when-creating-a-user
There's an open feature request
here: https://tickets.puppetlabs.com/browse/PUP-1331
Feel free to add yourself as a watcher and add a comment describin
Things should be back to normal, please let us know if you're still seeing
problems
--eric0
On Monday, April 27, 2015 at 9:15:12 AM UTC-7, Michael Stanhke wrote:
>
> Hey,
>
> We're working on fixing this right now. I'll post more when we've resolved
> the issue.
>
> On Mon, Apr 27, 2015 at 8:
Hi Vince and John, thanks for this feedback. There's quite a few things
under discussion in this thread but I think we can unpack them.
On Monday, April 27, 2015 at 9:34:13 AM UTC-7, jcbollinger wrote:
>
>
>
> On Friday, April 24, 2015 at 12:44:08 PM UTC-5, Vince Skahan wrote:
>>
>> On Thursday,
pen against the release here:
https://tickets.puppetlabs.com/issues/?filter=14021
<https://tickets.puppetlabs.com/issues/?filter=14021>
Eric Sorenson - eric.soren...@puppetlabs.com
<mailto:eric.soren...@puppetlabs.com> - freenode #puppet: eric0
puppet platform // coffee // techn
Many of you probably saw this on The Twitternets but I figured I would post
here as well: There are now release candidate builds of Puppet 4 and
Puppet-Server 2 available for EL7. The long-form writeup is at
bit.ly/1FBUJUN or you can jump straight to the installation
instructions: http://docs.p
Ugh, thanks for pointing this out, this is really old and is not true any
more. Looks like Mike Hall just pushed a docs change to remove this
reference.
As Den pointed out, the main feature that people used the Ruby DSL for
(loops/iteration) is now available in the Puppet 4 parser.
On Saturday
Hi Chris, there are a few different resources, depending on what
language and what specific resources you're interested in.
We now have many of the docs on the main puppetlabs documentation site
available in Spanish: http://docs.puppetlabs.com/es/
There's an active Brasilian puppet user group w
On Friday, March 13, 2015 at 10:21:26 AM UTC-7, Tim Skirvin wrote:
>
> Eric Sorenson writes:
>
> > Diversity is very important to us, so this year's survey also asks about
> > gender and diversity in tech.
>
> I am still concerned that this is being ac
es will get the survey results once they're all tallied.
Plus you'll be entered to win prizes, including Raspberry Pi and Arduino
Starter Kits, a $200 Amazon gift card, and more.
Thanks and we look forward to your feedback.
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #pupp
Hi Vishvendra, there is lots of activity on #puppet -- are you sure you are
connected to a Freenode server, which is connected to the rest of the
network?
You can check this with '/list #puppet' in your IRC client, it should show
~1000 users and this topic:
03:33 [freenode] -!- #puppet 1053 Pu
/release_notes.html#puppet-374
You can see the full list of changes on the release's JIRA page:
https://tickets.puppetlabs.com/browse/PUP/fixforversion/12033
If you're installing Puppet for the first time, follow the Installation Guide:
https://docs.puppetlabs.com/guides/install_puppet/pre_install.h
On Wednesday, January 21, 2015 at 5:40:27 AM UTC-8, Mike Hendon wrote:
>
> Triggering a refresh when you've changed manifests is also a pain.
>
Mike do you mean using the environment refresh API is a pain?
https://docs.puppetlabs.com/puppetserver/latest/release_notes.html#new-feature-admin-api
Looks like you got some good responses on your Ask question... All good now?
On Tuesday, December 16, 2014 3:22:26 PM UTC-8, red wrote:
>
> I guess I really don't need to list the nodes. I just wanted to try out
> the PE3.7 rest api. What I really need to be able to do is add
> nodegroups. I
OT go through any of the Puppet APIs? If so, STOP DOING
THAT! Just kidding, sorta. But it would be very interesting to know whether
you're using things like the `serial` or `inventory.txt` files in your scripts
or workflows.
Feel free to follow-up here or on
https://tickets.puppetlabs.com/
is release, check out the JIRA page:
https://tickets.puppetlabs.com/browse/SERVER/fixforversion/12023/
To install and start using Puppet Server instead of Apache+Passenger or
Webrick, follow this guide:
https://docs.puppetlabs.com/puppetserver/1.0/install_from_packages.html
Eric Sorenson - eri
ce ordering docs.)
> Organize your code into classes, and keep top-scope declarations to a minimum.
I totally agree with all of this.
Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles
--
You received this message because
Hi Kyle --
On Friday, November 21, 2014 1:46:19 PM UTC-8, Kyle Purdon wrote:
>
> TL:DR Using the --ordering = manifest option does not seem to apply to
> module commands.
>
> Using this parameter I would expect puppet to apply my manifest (site.pp)
> in the order it is written (script like exec
On Wednesday, November 19, 2014 9:02:00 AM UTC-8, Tim.Mooney wrote:
>
>
> Since RHEL 6.x has alternate versions of some packages (including ruby)
> available via its Software Collections Library (SCL), I'm tempted to
> try switching our puppet master to use the "ruby193-*" packages from
> SCL.
1 - 100 of 250 matches
Mail list logo
