Puppet: System Administration Automated

Support

Ticket #526 (closed enhancement: fixed)

Opened 2 years ago

Last modified 2 years ago

[PATCH] null schedule, a schedule that will never run.

Reported by: pizza Assigned to: luke
Priority: normal Milestone:
Component: puppet Version:
Severity: normal Keywords: schedules puppet
Cc: ramon@hyves.nl Triage Stage:
Attached Patches: Complexity:

Description

As discussed on irc last week , we require that some pieces run on demand (ie deployments), they should never run except by human interaction.

Our solution to integrate this with the regular-runs and pull architecture of puppet, is a combination of a schedule with tags and "puppetrun --ignoreschedules". This solution requires a schedule that will never run, hence the patch.

An example case:

schedule { "run-never":

nullschedule => true, }

exec { "/bin/echo deploying":

tag => deploy, schedule => run-never ,

}

this can then be run on demand using: puppetrun --host client.domain --tags deploy --ignoreschedules

Attachments

nullschedule-svn.patch (0.7 kB) - added by pizza on 02/26/07 17:16:00.

Change History

02/26/07 17:16:00 changed by pizza

  • attachment nullschedule-svn.patch added.

02/28/07 01:15:06 changed by luke

  • status changed from new to closed.
  • resolution set to fixed.

Fixed in [2238]. Added a period of 'never', rather than adding a new pararamter using the patch.