I use a combination of both solutions to achieve a similar result.
I tag modules based on internal development cycle, and then I put them all
on a directory on the server (e.g. /etc/puppet/modules/stable).
each module would have a version as a suffix (e.g. ssh_1.5)
then I automatically build env
> Also I believe there is work to implement module or class metadata which may
> provide what you're
> looking for--but I'm not sure how far off that is.
So do I.
And I think there's really a need here.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users
> there is the config_version
> optionhttp://docs.reductivelabs.com/references/stable/configuration.html#co...
> which gives you the possibility to give the possibility to generate a
> certain version for the current used manifests.
Great ! I think it's the thing I need :)
Thanks a lot,
--
Yo
