Feature #2213
Temporarily stop/start a service as a dependency to another action
| Status: | Rejected | Start date: | 04/30/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.24.7 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
I have a service defined as running but elsewhere I need to temporarily disable this service, take some action and then re-enable the service afterwards.
At the moment I am having to use execs for this but I’d rather use service if possible?
History
Updated by James Turnbull over 2 years ago
- Status changed from Unreviewed to Needs Decision
- Assignee set to Luke Kanies
I have a feeling I know the answer but…
Updated by Luke Kanies over 2 years ago
- Status changed from Needs Decision to Rejected
It’s not possible to do this at this point, because the service would need to be before and after your other resource – stop the service before, do something, stop the resource after.
We’re nowhere near being able to do something like that.