Repository navigation
Allow reviewed first-release health checks and public auth metadata - #46
Merged
Merged
Conversation
This was referenced Nov 4, 2026
Prepare timeline-wall-api develop deployment with OIDC v2.0.5
topcoder-platform/timeline-wall-api#45
Merged
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.
First deployments can currently stop before publishing because the live task has no container health check, even when the new image introduces the endpoint. Add optional
--bootstrap-health-checksto install a reviewed missing check with the new scanned image. Existing checks cannot be replaced; all identity, scan, concurrency, registration readback, running digest and circuit-breaker failure checks remain enforced. No IAM permissions are added.Status also has public issuer/audience URLs whose names include TOKEN. Permit only the three observed names with HTTPS values without user information, query strings or fragments, plus numeric TOKEN_CACHE_TIME. Other secret-like plaintext settings remain forbidden, and deployment roles retain explicit denial of secret-store access.
Validation: all 92 tests passed inside the pinned CircleCI AWS executor with networking disabled, including the AWS CLI parsing test and 10 new regression tests covering configuration preservation, opt-in validation, scan failures, readback tampering, rollback, duplicate JSON keys and the public-setting boundaries.
After merge, publish a new patch release and update the consumer pins. Existing consumers retain their current behavior until they explicitly opt in to health-check bootstrap.