Repository navigation
deploy-lambda: web identity only, no stored-key fallback (federation phase 4) - #118
Merged
Merged
Conversation
…phase 4) The app-secrets access key was a fallback for the switch. Every Lambda app has now deployed through its role and no Secret on kiac-dev or kind-prod holds an AWS key, so the fallback could only ever hand a deploy a long-lived key again. Removed: deploy-lambda no longer mounts app-secrets, and the credential helper fails with an error naming the missing piece (account ConfigMap, ServiceAccount, or the function's role). New test charts/glidepath-catalog/tests/aws_credentials_test.sh (in catalog-ci): 10 cases, 7 of which fail against the old templates. Docs: cloud-deploy-identity.md (redrawn flowchart), cicd-yaml-reference.md, security.md, known gap 43 (Lambda closed; ECS and Azure remain), schema description. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 16, 2026
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
1 participant
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.
Phase 4 of the deploy federation (
SPEC-glidepath-deployer-federation.md).Why now: every Lambda app (smoke-fn, both targets) has deployed through its role. The first federated production deploy was
promote-prod-0-deploy-cc5kjtoday. No Secret on kiac-dev (209) or kind-prod (104) holds an AWS key, and no ExternalSecret pulls one. The fallback could only ever hand a deploy a long-lived key again.Change
glidepath-catalog.awsLambdaCredentials: web identity only. Each missing piece fails with its own message and fix: the account ConfigMap (clusters.yamlaws.accountId), the ServiceAccount (taskRunSpecs), or STS refusing the role (the target's-deployRole).deploy-lambdano longer mountsapp-secrets.charts/glidepath-catalog/tests/aws_credentials_test.sh, wired intocatalog-ci: 10 cases against a stubaws, including "never reads a stored key". 7 of them fail against the old templates.cloud-deploy-identity.md(fallback section rewritten, symptom table, flowchart redrawn without the fallback),cicd-yaml-reference.md(no secrets for aws-lambda),security.md, known gap 43 (Lambda closed; ECS and Azure remain), schema description (text only, no validation change, so no toolbox rebuild).Canary: the catalog-versioning canary can't exercise this, because POL-10 lets
glidepath-cloud-deployerrun only thedeployPipeline resolved fromplatform-catalog. Verified live after merge with a real deploy instead.🤖 Generated with Claude Code