Hi Jay,
You could simplify things a little using 'unless' which acts like the
reverse of 'if'. You'd place your resources within the unless block so that
they'd only be included in your catalog if your Fact or variable evaluated
to false.
http://docs.puppetlabs.com/puppet/3/reference/lang_conditio
Hi,
I have a puppet module with more than 15 blocks of resources.. based on a
validation I want puppet to decide to continue next blocks or skip with a
warning(with out failing).
currently I am doing this with a big if block.
class mymodule {
if $::flag_enabled {
package {...}
files
Also, to purge users, you say
resources { ‘user’:
purge => true,
unless_system_user => ... # This keeps system users from being purged.
# By default, it does not purge users whose UIDs
are less than or equal to 500,
# but you ca
The “trick” is setting ( ensure => absent, ) for the users you want to purge.
How you do that depends on how you set it up to begin with.
On Oct 9, 2013, at 5:13 PM, Boudewijn Ector wrote:
> Hi Guys,
>
>
> I'm trying to get this done but don't know how to get there:
>
>
> Puppet is used to
Thanks John and Paul,
I would like to use the console, and I think wrapping the resource (defined
type) declaration in a class is still problematic for me because the parameters
I would like to pass in still exist at the class level, thus causing a problem
if I use different parameters for th
Hi Guys,
I'm trying to get this done but don't know how to get there:
Puppet is used to manage a new webserver using nginx+php-fpm , on which
each website has it's own user which is used to run the php-fpm pool.
Sure I can add users to the manifest so site foo.bar.tld will get a user
foo_b
Would you mind filing a pull request on this? If you already have please
ignore.
If you don't feel comfortable with that, please file an issue with the code
you used to fix it and we will take a look at it. Thanks!
On Tue, Oct 8, 2013 at 3:49 PM, Jason Harmon wrote:
> Ran into a problem with
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
cannot generate tempfile
`/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie
5i-9'
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Security Problem?Suggestion
I had this come up a couple of weeks ago.
Basic of the problem was that the source file it was looking for didn't
exist.
In depth, the file it should have been grabbing did exist, but it wasn't
being evaluated correctly due to a missing rb file in facter. I was
evaluating the source as
puppet
Il giorno mercoledì 9 ottobre 2013 17:16:20 UTC+2, alessandro mazzoli ha
scritto:
>
> Hi,
> i'm a newbie about Puppet( 1 month ~)
> i got error on generate temp file, i'll explain my situation:
> -i have a puppetmaster(version: 3.3.0),executed on root
> and a puppet agent(version 2.7) provision
Hi,
i'm a newbie about Puppet( 1 month ~)
i got error on generate temp file, i'll explain my situation:
-i have a puppetmaster(version: 3.3.0),executed on root
and a puppet agent(version 2.7) provisioning by vagrant,executed on root
-my site.pp, where webserv is a parametrized class, and typews is
Hello,
I am trying to extend my puppet installation by utilising hiera for dynamic
data for particular hosts. To that end, I'm testing hiera with the
puppetlabs ntp module. However, I am getting this error:
"Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
"false," i
In an effort to try and track catalog changes we did the following:
* Make agents archive their cached catalog using the postrun_command
configuration
* Dump the certname_catalogs table periodically
* Compare the catalog similarity hash with the previous state
* In case a hash changed, check the
On Tuesday, October 8, 2013 1:59:58 AM UTC-5, AMARASINGHAM, Chandra wrote:
>
> Hi,
>
>
>
> I would like to use a defined type and enter parameters from the puppet
> console. So far I can only use defined types in a class because the puppet
> console only seems to allow assigning configurati
On Tuesday, October 8, 2013 6:08:56 PM UTC-5, Paul Oyston wrote:
>
> I'm really only wanting an up to date set of facts once the puppet agent
> has finished making changes to the system, I'm not wanting to modify the
> catalog run process by modifying facter values during the run process. I'm
On Tuesday, October 8, 2013 12:06:18 PM UTC-5, wilddog64 wrote:
>
> It seems that instead of add the following line in [master], they have to
> be in [agent] for dynamic environment to work. So the document does not
> reflect what PE 3.x is.
>
> On Oct 8, 2013, at 7:52 AM, wilddog64 >
> wrote
On Tuesday, October 8, 2013 8:21:43 AM UTC-5, Andreas Dvorak wrote:
>
> Hi,
>
> there is a problem
>
> If I want to add a second user with the same group to the same server I
> get this error:
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Duplicate declaration
indepth kibana.. well wouldn't that mostly be elasticsearch in depth you'd
need? and Kibana is such a moving target, that it would probably have
changed majorly, before a book came out :)
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsu
Morning all,
Thought I'd drop around a quick note to cover a couple of things off :)
Firstly, I've released v0.4.1, which includes a fix when working with
Puppet >3.2.0
However further testing has highlighted a bug within Puppet, which means
that my NetApp device module will not work with any
Hi,
i'm trying to enable a basic LDAP authentication mechanism for our puppet
opensource dashboard.
My /etc/httpd/conf.d/puppetdashboard.conf looks like this: (i changed
sensitive data)
Listen 3000
>
>ServerName puppet.local.domain
>DocumentRoot /usr/share/puppet-dashboard/public/
>
20 matches
Mail list logo