This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 41
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
37 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
- Feature Name: update-engines-without-minion-restart | ||
- Start Date: 2019-07-16 | ||
- SEP Status: Accepted | ||
- SEP PR: https://github.com/saltstack/salt-enhancement-proposals/pull/16 | ||
- Salt Issue: | ||
|
||
# Summary | ||
[summary]: #summary | ||
|
||
Being able to restart minion engines without having to restart the minion itself. | ||
|
||
# Motivation | ||
[motivation]: #motivation | ||
|
||
As a user I need to run a new engine on a minion, but restarting the minion needs to be done carefully and may not happen when I need it. | ||
This is already possible with beacons. | ||
|
||
# Design | ||
[design]: #detailed-design | ||
|
||
The engine configuration could be either in the configuration or in the pillar. | ||
When refreshing the pillar, loop over the engines configuration and start or stop the engines according to the new configuration. | ||
|
||
## Alternatives | ||
[alternatives]: #alternatives | ||
|
||
The alternative is to manually restart the salt minion, with all the problems this can bring. | ||
|
||
## Unresolved questions | ||
[unresolved]: #unresolved-questions | ||
|
||
If this is too problematic to run on every pillar refresh, then an additional function could be provided to only refresh the engines. | ||
|
||
# Drawbacks | ||
[drawbacks]: #drawbacks | ||
|
||
The engines documentation would need to add this new possibility to configure the engines using pillar. |