Actually I just went back and looked
[1;31mError: /Stage[main]/Yum/Acl[chocolatey.config]: Could not evaluate:
The parameter is incorrect. -ReportEvent
Yum?
On Fri, Sep 25, 2015 at 3:38 PM, Rob Reynolds wrote:
> So let's remove target and give it a shot.
>
> acl { 'c:/ProgramData/chocolatey/co
So let's remove target and give it a shot.
acl { 'c:/ProgramData/chocolatey/config/chocolatey.config':
On Fri, Sep 25, 2015 at 1:31 PM, jmp242 wrote:
> I tried with the simplified version:
> Enter code here... acl { 'chocolatey.config':
> target =>
> 'C:/ProgramData/chocolatey
> We recently upgraded to PE2015, and as such have upgraded our local puppet
> gems to match (4.2.2). Unfortunately a few of our specs that were previously
> passing are now failing, mostly in regards to stages:
>
> "Evaluation Error: Error while evaluating a Function Call, Could not find
> stage f
I tried with the simplified version:
Enter code here... acl { 'chocolatey.config':
target => 'C:/ProgramData/chocolatey/config/chocolatey.config',
permissions => [
{
identity => 'SYSTEM',
rights => [
'full']
}
(Not a programmer, please bear with me. I couldn't find answers in the code for
1.5.1 or 2.0.3.)
How often does r10k update its cache? It looks like once per invocation.
Is there a way of telling an r10k invocation to use the cache directly?
I could use local git repositories presync'ed myself
Just checking in David, wondering about the future parser progress. How is
it going?
Also may have found a bug, though it may be down to the future parser.
I'm seeing a parse error in sonarqube for a manifest that runs fine under
puppet 3.x and puppet with the future parser enabled.
On Fri
Hah! That's a valid point. Unfortunately for me, the actual manifest has
the comma after the password (I just failed when obscuring it, apparently).
On Thursday, September 24, 2015 at 8:33:48 PM UTC-7, red wrote:
>
> You might need a comma after 'obscured_because_security' :)
>
> On Thu, Sep 24,
Hi guys,
this is my first try of puppet, but installation failed as log shows below:
** /opt/puppetlabs/puppet/bin/erb -T -
'/tmp/pe-installer-piDZHaqs/install/erb/puppet_enterprise.pp.erb'
'/tmp/pe-installer-piDZHaqs/install/erb/pe_repo.pp.erb'| {
PATH=/opt/puppetlabs/puppet/b
Well . . . It doesn't give me anything else helpful. Out of 142KB of log,
this seems relevant:
{ identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects =>
'self_only' },
{ identity => 'NT AUTHORITY\SYSTEM', rights => ["full"], affects =>
'self_only' },
{ identity => 'NT AUTHORITY
On Thu, Sep 24, 2015 at 7:25 AM, jmp242 wrote:
> So per my previous post, I'm now trying to replace the file POSIX
> permissions with ACLs. I'm apparently missing something though. I want to
> replicate what I had before in the new supported method, i.e.:
>
> owner => 'SYSTEM',
>
10 matches
Mail list logo
