WIP: Add capability to run plugins between lifecycle steps #23
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
* We can run plugins between the single steps in the "lifecycle" of the rollout: - after the templates are rendered - after the resource files are written to disk - after the resources are rolled out to kubernetes
mattthias
force-pushed
the
matthias/add_hooks
branch
from
85178a3 to
d24e04b
Compare
This was referenced Jan 27, 2017
Provide a way to check if the Docker image exists in the registry before rolling out a deployment
#5
Open
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.
rollout:
ToDo: Add documention to README how Python plugins and arbitrary plugins are supposed to work.