Repository navigation
Automatically deploy verified OpenSensor API images from main - #79
Merged
Merged
Conversation
This branch was successfully deployed
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.
Main builds previously stopped after publishing the OpenSensor API image. Add an automatic production deployment after both lint and image build succeed, using the published immutable registry digest. Pull requests never deploy, and main runs are serialized so an active rollout can finish.
The deployment waits for Kubernetes readiness, verifies the selected digest, then checks the application health endpoint and Sentry release configuration inside the running container. Existing Secrets, resource settings, and deployment strategy are retained. The build action now exposes its digest through GITHUB_OUTPUT and the workflow uses supported checkout/Python actions.
Validation: actionlint and
git diff --checkpass; both workflow files parse. The PR runs lint and the container build; merging activates the production rollout.