Repository navigation
Use effective ECS checks in deploy completion hints - #226
Merged
Merged
Conversation
Generated essential supervisor checks use the checked ECS waiter path and must not emit an unchecked-application hint. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
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.
Generated checks on an essential container now classify HTTP API deploys as health checked. The completion message and follow-up hint both use the effective task definition, so supervisor-checked services receive the checked deployment message.
Validation: ECS waiter/health characterization, synthesized task checks, fast-deploy hint tests and the integrated gate passed. This is the first layer of #226 → #227 → #228.
🤖 Generated with Claude Code