Ok, got it. Thanks for that clarification. I totally missed that
distinction.
Rajul
On Mon, Nov 19, 2012 at 6:34 AM, jcbollinger wrote:
>
>
> On Sunday, November 18, 2012 12:13:20 PM UTC-6, Rajul Vora wrote:
>>
>>
>> From official documentation:
>>
>> User <| (group == dba or group == sysadmin)
On Sunday, November 18, 2012 12:13:20 PM UTC-6, Rajul Vora wrote:
>
>
> From official documentation:
>
> User <| (group == dba or group == sysadmin) or title == luke |>
>
>
You are missing Nick's point. In your example, you declare *secondary*groups
for your users via their 'groups' properties,
>From official documentation:
User <| (group == dba or group == sysadmin) or title == luke |>
On Sun, Nov 18, 2012 at 8:55 AM, Nick Osborn wrote:
> On Friday, November 16, 2012 9:04:44 PM UTC, Rajul Vora wrote:
>>
>> define realize_helper( ) {
>> User <| group == $name |>
>> }
>>
>
>
On Friday, November 16, 2012 9:04:44 PM UTC, Rajul Vora wrote:
>
> define realize_helper( ) {
> User <| group == $name |>
> }
>
ITYM 'groups' not 'group'.
--
Nick
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion
Unfortunately, this does not work either. Here's a complete standalone
puppet manifest you can do "puppet apply" on. No users are actually being
realized.
I don't believe "User <| group == $name |>" works.
:(
Rajul
node default {
class { 'usergroups':
}
}
class virtusers {
group { 'A'
Yes, I was actually thinking of doing that after I sent my reply to you -
based on your mymodule::usergroup defined resource idea. Thanks for
confirming that idea. I'll implement it and it will work for what I am
trying to do.
Simple is better.
Rajul
On Friday, November 16, 2012 11:16:36 AM U
On Friday, November 16, 2012 11:07:18 AM UTC-6, Rajul Vora wrote:
>
>
> Thanks for the effort in explaining these alternatives. I apologize I
> didn't do justice to explaining the bigger picture in the first place.
>
> So here it goes:
>
> Goal: Use hiera to provision different groups of users i
Thanks for the effort in explaining these alternatives. I apologize I
didn't do justice to explaining the bigger picture in the first place.
So here it goes:
Goal: Use hiera to provision different groups of users in different
environments.
Approach: First create virtual users from hiera that
On Thursday, November 15, 2012 6:01:24 PM UTC-6, Rajul Vora wrote:
>
>
> I want to do something like this:
>
> class foo ( $collection ) {
>
> User <| $collection |>
>
> }
>
> where $collection would be a string like "group == admin or group ==
> powerusers"
>
> Doesn't work. Is there an altern
