Name the deployed image tags in the checked-in stack - #12
Merged
Merged
Conversation
deploy/portainer-stack.yml still said 0.1.7, which was never deployed. The running stack was 0.1.2 and is now 0.1.9. A stack file that names a tag nobody runs is worse than no stack file: it is the first place anyone looks to find out what production is. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
deploy/portainer-stack.ymlsaid0.1.7, a tag that was never built or deployed. Production was actually running0.1.2and is now on0.1.9.This cost real time during the 0.1.9 deploy: the stack file was the first place I looked to find out what production was running, and it was wrong by four releases.
🤖 Generated with Claude Code