I can think of three options: 1) Break the user / group definitions into their own classes, and "require" the group class in your user definition class.
2) In some cases, Puppet does an implicit require-- it's possible your code would work as-is, and the catalog would recognize the need to create groups first. I don't know if this is expected behavior or not any longer, but perhaps one of the devs could comment. Since they're defined in the same class, I would hope Puppet would be smart enough to recognize the need to define a group before defining a user that's a member of that group. 3) Don't worry about it-- let it fail. I run puppet twice per hour, and if it can't define the user because the group is missing, it can still define the group on the first pass. Then the next pass, the user will get created, because this time the group already exists. Ugly, mildly irritating, but still effective. Obviously, this isn't a good option if you're paying attention to the exit status of the puppet run, but if you're just running the puppet agent every so often, should be fine. -- 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/f7bc6ea2-9d6a-411a-878c-5368f30f5a09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
