Wouldnt it work anyways (if manifest order or not) because the file
typeauto-reqires its parents?
https://docs.puppet.com/puppet/latest/types/file.html#file-description
-Thomas
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe fr
- Original Message -
> From: "John Gelnaw"
> To: "puppet-users"
> Sent: Tuesday, 10 January, 2017 01:17:58
> Subject: Re: [Puppet Users] Over-engineering rant
> On Monday, January 9, 2017 at 2:39:38 PM UTC-5, R.I. Pienaar wrote:
>>
>>
>> Because if i can convince your client to connect
I think certificate handling is a valid critique of puppet's security
implementation. Running a public key infrastructure of any sort is
difficult. Things like expired CAs and a lack of intermediate signing CAs
does expose puppet administrators who are lacking those fairly rare skill
sets to some d
On Monday, January 9, 2017 at 2:39:38 PM UTC-5, R.I. Pienaar wrote:
>
>
> Because if i can convince your client to connect to $evil_ca, then what?
> How's it to know its a new legit ca and not a new bad ca?
>
The same way it "knew" when you originally provisioned it-- It didn't. In
fact, the a
*tl;dr* what is the officially endorsed way to leverage beaker to run tests
against PE (sp. 2016/7.x) in a CI type of setup?
I've beaten my head against beaker-{pe,rspec} etc. enough that I assume
others may be running into similar problems or guesswork, so bear with me:
Thus far I've been able
- Original Message -
> From: "John Gelnaw"
> To: "puppet-users"
> Sent: Monday, 9 January, 2017 20:14:00
> Subject: Re: [Puppet Users] Over-engineering rant
> On Monday, January 9, 2017 at 10:10:08 AM UTC-5, R.I. Pienaar wrote:
>>
>>
>> so we're on the same page are you just saying in
Hi Ryan,
On Mon, Jan 9, 2017 at 9:40 AM, Ryan Vande wrote:
> I went to take the test last week, they had questions about live
> management. To be honest the testing center monitors were so small all of
> the content would not fit on the page, I spent so much time resizing
> windows, I ran out of
On Monday, January 9, 2017 at 10:10:08 AM UTC-5, R.I. Pienaar wrote:
>
>
> so we're on the same page are you just saying in general the NTP module
> has too much
> going on and its too huge for a "simple" piece of software?
>
Mostly, it was the unexpected syntax. Somehow, I completely missed a
On Thursday, January 5, 2017 at 11:28:33 AM UTC-8, Rob Nelson wrote:
>
> With puppet4 showing up in vendor repos, is it safe to assume those
> versions will not have an aio_agent_version fact?
>
> On Thu, Jan 5, 2017 at 1:37 PM, Gabriel Schuyler > wrote:
>
>> Hey Vince, the $::aio_agent_version f
I went to take the test last week, they had questions about live
management. To be honest the testing center monitors were so small all of
the content would not fit on the page, I spent so much time resizing
windows, I ran out of time to finish the test.
I seen what the test is composed of and
We use something that's halfway between the second and third options.
We use standardized namespaces in Hiera that group together logical sets
of data (we use it mostly for distributed app configuration, but you
could easily apply this to system configuration), then we pull that into
our profi
Live Management was deprecated back in PE3.8 and I don't believe it has
returned. PE3 support expired on 1/1/2017. I would hope it's not on the
test because of that, even if it's still in some study guides.
Rob Nelson
rnels...@gmail.com
On Mon, Jan 9, 2017 at 10:34 AM, Ryan Vande wrote:
> I ha
I have installed puppet enterprise 2016.4.2 and am using the free ten nodes
license.
I am studying for the ppt-204 and have seen questions related to live
management.
I have searched high / low / left / right , where do live management go?
All examples shown for live management show that is av
- Original Message -
> From: "John Gelnaw"
> To: "puppet-users"
> Sent: Monday, 9 January, 2017 15:56:34
> Subject: Re: [Puppet Users] Over-engineering rant
> 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 b
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 -
> about 20 months to be precise - and most of the significant language
> c
Hi Henrik,
> A non-existent type will in some versions of puppet be taken as being a
> resource type.
>
> One thing you can check is that your module (where you are using Stdlib::XXX
> types have declared a dependency on Stdlib in its metadata. If it does not
> have this it will not find type
On 09/01/17 13:02, Tiago Delboni wrote:
Hi!
I'm having trouble using type Stdlib::Windowspath, from module
puppetlabs/stdlib, as a parameter type in a manifest. Is this "custom
type" really available? In
https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/types/windowspath.pp
it is defin
Hi!
I'm having trouble using type Stdlib::Windowspath, from module
puppetlabs/stdlib, as a parameter type in a manifest. Is this "custom type"
really available? In
https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/types/windowspath.pp
it is defined using the "type" word, which, acco
Hi,
I wonder what approaches you are currently using for sharing common information
among multiple Puppet profiles:
To come up with some examples which will need to be maintained for multiple
profiles:
- HTTP proxy settings
- IP ACLs for whitelists (eg. IP of monitoring systems, trusted hosts)
-
On 09/01/17 02:52, chris smith wrote:
Hi,
This seems like a pretty simple thing but I can't figure out why this is
throwing a warning.
I'm using puppet 4.8.1 installed from the puppetlabs-pc1 on scientific
linux 6.
# puppet -V
4.8.1
# rpm -q puppet-agent
puppet-agent-1.8.2-1.el6.x86_64
My fi
20 matches
Mail list logo
