I have a need to mark certain resources with an expiry / deprecation date so when we no longer need them applied we get some kind of reminder.
One concrete use case for me is the promotion of a cronjob from an adhocresource pushed via puppet to a packaged version that comes from an rpm. Once we release that rpm we no longer need the puppet version. I've put together a small proof of concept for deprecating individual resources - http://pastie.org/7719128 - and I thought I'd ask the list what they thought of the idea and if the poc - with a little tidying, validation / better docs and such forth - would be accepted. I've had some great feedback from Richard Clamp and we've discussed having a possible function or type to mark entire classes as deprecated - Type - deprecate { 'stop foo': warn_from => 'yyyymmdd', fatal_from => 'yyyymmdd' } Function call class foo { deprecate '20140101', 'The future has arrived, use bars!' ... } What does the list think? Dean PS Maybe expires is a better name for this. Commence bike shedding ;) -- Dean Wilson http://www.unixdaemon.net Profanity is the one language all programmers understand --- Anon -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
