Repository navigation
feat: add secured Azure deployment lifecycle - #6
Merged
Merged
Conversation
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.
What changed
Adds one real-only Azure Container Apps lifecycle for the bundled FastAPI workload: deterministic deployment candidates, saved-plan hash binding, DevSecOps eligibility, approval-gated Terraform apply, ACR image digest handling, Azure observation, health verification, and explicit cleanup.
Why
This turns the existing local, security, and Terraform capabilities into one coherent deployment workflow while preserving the ToolService and approval architecture.
Validation
httpxdependency, so the two FastAPI test modules cannot collect locally.The PR is draft pending CI and an opt-in credentialed Azure acceptance run.