On Oct 4, 2009, at 5:17 PM, Dan Bode wrote:
> I wanted to toss a possible use case into the mix:
>
> If puppet had some internal knowledge of module versions, it could
> provide puppet events some awareness about when puppet source code
> changes.
>
> This could be useful in differentiating between events that occurred
> as a result of a new version of a module versus random events
> (events not related to source code changes in the module are
> probably more important)
It would, at the least, be a bit of metadata you could add to the
configuration changes, in addition to the overall repository version
(which would begin to have a bit less meaning if people are keeping
most modules outside the main repo).
You're more talking about a three-way merge operation (current state,
desired state, previous state), which also needs to be supported but
(I think) is a different feature.
>
> Anyways, I will open a ticket for this as a feature request if one
> does not exist already.
That'd be great.
--
It's a small world, but I wouldn't want to paint it.
-- Stephen Wright
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
