On Mon, Mar 31, 2014 at 10:09 AM, Martin Langhoff <[email protected]> wrote: > This is really awkward for what I see as a "natural" operation. Am I doing > something wrong in my setup? > > And also... this is funny, but I discovered a change including this syntax > had already been rolled out into production, so I thought I would find all > the virtual user accounts created. In fact I did not.
Ok, I found both the explanation of why this is not creating users in our env, and I guess a good workaround to this situation. In our env, virtual users are not realized directly, they are realized through a "define ssh_user" that manages authorized_keys and assigns them to wheel. That layer of indirection _is_ in Puppet's state, but it means that the virtual user does not have the membership set in the "virtual" definition. At some point of the discussion I also lost sight of the conditionality of the materialization (will only materialize /matching/ resources) and I was temporarily a bit more anxious than I should have been. This is a relief. I still consider resource collectors dangerous, but usable in clearly defined situations. m -- [email protected] - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACPiFCJNXs6dnpKYri89MaHKGpwgecKG-iVwFwqYfbWZ%3DBwcFg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
