[Puppet-dev] mcollective-actionpolicy-auth argument filter

2015-07-31 Thread Tom Denley
I just raised a ticket for this (https://tickets.puppetlabs.com/browse/MCOP-530), but realised I should have posted in the group first. https://github.com/puppetlabs/mcollective-actionpolicy-auth plugin supports ACLs based on actions for a given agent, but does not allow access based on the ar

Re: [Puppet-dev] Re: Accessing resource attributes

2015-07-31 Thread R.I.Pienaar
- Original Message - > From: "Henrik Lindberg" > To: "puppet-dev" > Sent: Friday, July 31, 2015 2:10:05 PM > Subject: [Puppet-dev] Re: Accessing resource attributes > On 2015-31-07 12:35, R.I.Pienaar wrote: >> I just noticed last night we can now access resource and class attributes: >

[Puppet-dev] Re: Accessing resource attributes

2015-07-31 Thread Henrik Lindberg
On 2015-31-07 12:35, R.I.Pienaar wrote: I just noticed last night we can now access resource and class attributes: define x($y) { } x{"foo": y => "bar"} notice(X["foo"]["y"]) this works, yay with the obvious parsing order caveats. This works too: define x($y) { noti

[Puppet-dev] Accessing resource attributes

2015-07-31 Thread R.I.Pienaar
I just noticed last night we can now access resource and class attributes: define x($y) { } x{"foo": y => "bar"} notice(X["foo"]["y"]) this works, yay with the obvious parsing order caveats. This works too: define x($y) { notify{$name: message => $y } } class one {