strategy: add new marker_file strategy
#1103
Open
+430
−7
Conversation
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
Add a simple, flexible strategy that checks the directory `/var/lib/zincati/admin/marker_file_strategy` for a JSON file (optionally containing an expiry timestamp key) named `allowfinalize.json` and allows update finalization if such file exists and has the proper permissions.
This explains how the `marker_file` strategy works and how to configure it.
Fixed conflict in tests/kola/server/data/ by using the script symlink instead of the directory symlink.
|
Any news here? This strategy would be very useful in combination with kured! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re-opening of #540 since the original fork was removed.
Original summary:
Add a simple, flexible strategy that checks /var/lib/zincati for
a JSON file (optionally containing an expiry timestamp key) named
allowfinalize.json and allows update finalization if such file
exists and has the proper permissions.
See #245 (comment) for the rationale for this new strategy.