Hi all,
I have the following fact to get the full path of the Puppet executable
being distributed via a module:
Facter.add("puppet_executable") do
> setcode do
> Facter::Util::Resolution.exec('/usr/bin/which puppet')
> end
> end
>
This fact is used to set the command attribute of the cr
This is an issue I run into pretty regularly. If your Puppet infrastructure
is even moderately complex, I'd recommend NOT equating a Puppet environment
to an operational environment, operational environment being the groups of
machines known as dev, qa, staging, etc.
For instance, in my infrast
don't think this is
currently possible?
On Aug 20, 2016 12:20 PM, "Christopher Wood"
wrote:
Lots about hiera data in this thread, how about modules? Having a common
environment for the common modules and using basemodulepath helps some, but
it's not everything.
On Sat, Aug 20
t multiple
times, the last being very recent.
On Saturday, August 20, 2016 at 6:39:03 PM UTC-4, Alex Samad wrote:
>
> On 20 August 2016 at 22:50, Chadwick Banning > wrote:
> > This is an issue I run into pretty regularly. If your Puppet
> infrastructure
> > is even mod
, August 20, 2016 at 9:04:34 PM UTC-4, Chadwick Banning wrote:
>
> As Rob Nelson mentioned above, you can differentiate between operational
> environments in Hiera as long as you have the appropriate facts available.
>
> If you differentiate Puppet environments and operational e
n Sun, Aug 21, 2016 at 11:20 PM, Alex Samad wrote:
> On 21 August 2016 at 11:04, Chadwick Banning
> wrote:
> > As Rob Nelson mentioned above, you can differentiate between operational
> > environments in Hiera as long as you have the appropriate facts
> available.
>
urce of truth, greatly limits the number of variables in play at
>> any given time and streamlines your pipeline.
>>
>> I would recommend a book on Continuous Integration and/or Continuous
>> Delivery as these are subjects far too deep and wide to properly cover here
>>
I looked at the PR (https://github.com/camptocamp/puppet-postfix/pull/50)
to add "Hiera support" and it appears that it just add some parameters that
take hashes that are used to auto-generate instances of defined types. I
wouldn't call this "Hiera support", I'd just call it "convenience
parame
x27;ll definitely look a it soon, but can you explain what the lines do?
>
> What would key_name be?
>
> Thanks!
>
> On Wednesday, October 19, 2016 at 8:01:34 AM UTC-4, Chadwick Banning wrote:
>>
>> I looked at the PR (https://github.com/camptocamp/puppet-postfix/pull/
Hi Nidhi,
I think Rob was referring
to
https://github.com/openstack/puppet-cinder/blob/master/manifests/backend/solidfire.pp.
This appears to be what is changing the config using a custom cinder_config
type. You can see the provider code that is updating the config
at
https://github.com/ope
>
> Autorequires: If Puppet is managing the user’s primary group (as provided
> in the gid attribute) or any group listed in the groups attribute then the
> user resource will autorequire that group. If Puppet is managing any role
> accounts corresponding to the user’s roles, the user resource
Would it be safe to consider this in a general context i.e. as enabling
agent-side function execution?
On Thursday, August 30, 2018 at 8:11:52 PM UTC-4, Lindsey Smith wrote:
>
> Hi all,
>
> We wanted to let you know about an upcoming capability, the Deferred type,
> that is now present in Puppet
extract a value from a
file agent-side?
On Fri, Aug 31, 2018 at 9:12 AM R.I.Pienaar wrote:
>
>
> On Fri, 31 Aug 2018, at 15:03, Chadwick Banning wrote:
> > Would it be safe to consider this in a general context i.e. as enabling
> > agent-side function execution?
>
> I
8 16:41:34 UTC+1, Chadwick Banning wrote:
>>
>> So for this example, there are some sort of limitations as to what the
>> 'vault_lookup' function is able to do internally? I had just assumed that
>> as long as the function returned a simple value, what the function does
You should be able to also set them
using https://forge.puppet.com/puppetlabs/postgresql#postgresql_conf.
On Tuesday, October 16, 2018 at 4:54:13 AM UTC-4, comport3 wrote:
>
> Hi All,
>
> We are integrating a new PuppetDB role, and note that there are some key
> tuning parameters we'd like to mo
If using a different Vault auth method is an option, you could use the
AppRole method and define a role and policies in Vault. The Puppet agent
then authenticates under a specific role (and instance of that role) that
is governed by the policy.
On Tuesday, October 9, 2018 at 8:12:39 AM UTC-4, c
>
> Since reading the reasoning here I've continued to think about this off
> and on and still have a hard time with the idea of hard-coding
> configuration. It seems like a bit of a paradox within puppet. When
> writing modules it is generally accepted to separate any configuration data
> f
17 matches
Mail list logo
