Skip to content

AWS dual-backend vault + shared platform-secret resolution - #745

Open
farchide wants to merge 2 commits into
masterfrom
feature/aws-vault-dual-backend
Open

AWS dual-backend vault + shared platform-secret resolution#745
farchide wants to merge 2 commits into
masterfrom
feature/aws-vault-dual-backend

Conversation

@farchide

Copy link
Copy Markdown
Collaborator

Adds an AWS Secrets Manager backend to the framework vault alongside the existing Azure Key Vault path (dispatched by [VAULT] type), plus shared platform-secret resolution — required for the customer vault to work on AWS/EKS (tokens, connector creds, etc.).

Commits: c14b6b9 (AWS dual-backend vault) + a .gitignore tidy for gadriel .security/ dirs.

🤖 Generated with Claude Code

farchide and others added 2 commits May 29, 2026 12:19
Add restapi_aws.py (AWS Secrets Manager helpers) and wire the vault dispatcher
to select aws vs azure via [VAULT] type. Add get_platform_vault_data() so
account-level secrets resolve from the shared platform prefix
(prancer/prod/platform), enabling one value (ENCRYPT-DECRYPT, SendGrid, OAuth
client ids) to serve every tenant when prancer-account is not deployed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@farchide
farchide requested a review from a team June 10, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant