Repository navigation
Document legacy and v2.0.9 deployment flows - #50
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.
Add before/after Mermaid diagrams to the README for the legacy 1.4.* ECS deployment and v2.0.9.
The legacy diagram follows the v1.4.21 client code: the broker returns AWS credentials inside a JWT, CircleCI extracts/configures them, and deployment commands call AWS directly. It explicitly marks the broker implementation as unverified.
The v2.0.9 diagram shows independent IAM provisioning, separate build and deployment jobs, production approval, direct OIDC/STS authentication, ECR digest/scan checks, ECS rollout verification, and runtime secret retrieval through the ECS execution role. The accompanying text distinguishes signed tokens from credentials and explains the limits of workflow approvals and token protection.
Validation: checked against the referenced legacy code and v2.0.9 implementation; verified both Mermaid code fences and
git diff --check. Documentation only; the published v2.0.9 tag is unchanged.