Update pipeline to tag images with gitsha and latest#5
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this do?
We need the ability to pin deployments to certain versions of our steampipe image.
For instance, when we're introducing new features, or updating our forked version with updates from upstream, we want the ability to gradually roll out the new image and test it with different services. If something breaks, we want the ability to roll back to old version.
This creates two tags: one with the gitsha and one with latest. The latest tag will always move up to the latest build, while previous builds are still accessible via their gitsha. This preserves our ability rollout latest automatically when this repo pushes a new image; but also gives us the ability to rollback to a known good version when needed.