Thanks, this is very helpful and my preliminary testing is showing that this is what is happening.
On Tuesday, February 21, 2017 at 6:50:16 AM UTC-7, jcbollinger wrote: > > > > On Tuesday, February 21, 2017 at 5:44:14 AM UTC-6, Chadwick Banning wrote: >> >> 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 will >>> autorequire those role accounts. >> >> >> > ^^^^ this. > > In other words, you don't need to explicitly specify relationships between > User and Group resources to ensure that the groups to which a given user > belongs are managed before the user himself. I can perhaps see an argument > for doing so anyway in a class coded as you describe for the original, but > it is foolish to go out of your way and complicate your manifests to > re-express relationships that are *already there*. It's even worse to > add altogether irrelevant relationships in order to facilitate doing so. > I'd simply add a comment to the manifest to document that you're relying on > the autorequirements. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6c0db0c1-bc2f-46f7-ae6b-dd250f86c671%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
