-
Notifications
You must be signed in to change notification settings - Fork 7
Harden production promotion image copy and readiness #356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
justin808
merged 9 commits into
main
from
jg-codex/use-native-production-image-copy-template
Jun 3, 2026
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
48f8ade
Use native Control Plane image copy in promotion workflow
justin808 81c3f99
Use staging token directly for promotion image copy source
justin808 59e1dfc
Harden production promotion image copy template
justin808 1d85351
Merge remote-tracking branch 'origin/main' into jg-codex/use-native-p…
justin808 8b89d21
Update generated command docs
justin808 ca0468f
Address promotion copy review feedback
justin808 ee11d62
Harden promotion env and readiness checks
justin808 f50e284
Pin Buildx action in promotion workflow
justin808 6cd8225
Handle digest-pinned staging image refs
justin808 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Likely wrong JSON path — will always show
"unknown"The Control Plane workload object returned by
cpln workload get -o jsondoes not have a top-level.healthkey. Health/readiness state lives under.status(e.g..status.ready,.status.readyLatest). The.health.readinesspath will resolve tonullon every poll, so the// "unknown"fallback always fires.This only affects the log line (not the readiness gate), but it makes the "waiting for latest deployment" message permanently say
readiness=unknownand removes a useful diagnostic signal. Consider dropping this field until the correct path is confirmed from a real cpln workload response, or verify the path against the API and correct it.