Draft feature docs: porter apply exit codes for superseded deploys#395
Open
mintlify[bot] wants to merge 1 commit into
Open
Draft feature docs: porter apply exit codes for superseded deploys#395mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Documents the new exit code
3returned byporter apply --waitwhen a deployment is superseded by a newer revision, so CI consumers can distinguish a canceled deploy from a genuine failure.Changes
porter applycommand reference with a table of0/1/3outcomes.3for superseded deploys is rolled out per project (feature-flagged) and falls back to exit0until enabled.$?to skip alerts when a deploy was replaced by a newer revision.Context
Upstream change makes
porter apply --waitexit3(instead of0) when a deploy is canceled by a newer one starting before it finishes. Previously CI treated a deploy that never shipped as a success. The behavior is opt-in per project via feature flag; other entry points (update-image --wait,porter app …,porter deploy) keep their existing exit1for now.cc @georgezhang for review.