Skip to content

Modularize secret providers behind a provider registry#57

Merged
jimpudar merged 1 commit into
mainfrom
jmp/modularize-secrets-provider
May 20, 2026
Merged

Modularize secret providers behind a provider registry#57
jimpudar merged 1 commit into
mainfrom
jmp/modularize-secrets-provider

Conversation

@jimpudar
Copy link
Copy Markdown
Collaborator

Summary

  • Introduce a provider-neutral secrets layer with SecretProvider, SecretProviderRegistry, and provider-qualified secrets.env mappings.
  • Move the existing macOS Keychain lookup behind a macos-keychain secret provider and route secret injection through the registry.
  • Update the default secret mapping format and documentation to support future providers like 1Password, AWS Secrets Manager, and libsecret.

Testing

  • Added unit coverage for provider-qualified secret parsing, registry dispatch, duplicate/unknown provider handling, and the macOS Keychain provider behavior.
  • Updated existing provider factory coverage to assert the secrets registry is present.
  • Validation passed: typecheck, lint, and unit tests.

@jimpudar jimpudar merged commit 9a4c41b into main May 20, 2026
2 checks passed
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