Tags are an interesting way to tackle this issue. Thanks for pointing that out.
On Monday, October 27, 2014 5:34:06 PM UTC-4, Ramin K wrote: > > On 10/27/14 7:43 AM, jcbollinger wrote: > > > > On Friday, October 24, 2014 12:51:27 PM UTC-5, Mark Rosedale wrote: > > > > Hello, > > > > I'm looking to start to implement scheduling for certain resources > > within puppet. My one question is this. > > > > If I have a schedule set on resource 'foo' does that prohibit that > > resource from being updated if I run puppet agent by hand? What I'm > > wondering is if I end up needing to do puppet work manually, but am > > outside of a my maintenance window do I have to edit my puppet code > > to apply foo or can I override it somehow? > > > > If you run the puppet agent with the "--ignoreschedules" option then it > > will (attempt to) apply /all/ resources in the catalog, regardless of > > any schedules. > > > > I am not aware of any built-in mechanism to selectively ignore a subset > > of schedules, but if that's something you anticipate wanting to do > > regularly then you could build something into your manifest set to > > support it, probably built around a custom fact. > > > > John > > Coupling the above with --tags $resource_name might give you the > granularity you need. > > https://docs.puppetlabs.com/puppet/latest/reference/lang_tags.html > > Ramin > > > -- 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/a6889100-33fb-4e92-b2d4-2c4768a2e307%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
