feat: add SecretManagerAccessor for GKE deployments#15
Open
rollingventures wants to merge 1 commit intomainfrom
Open
feat: add SecretManagerAccessor for GKE deployments#15rollingventures wants to merge 1 commit intomainfrom
rollingventures wants to merge 1 commit intomainfrom
Conversation
Adds SecretManagerAccessor template for reading secrets from Google
Secret Manager in GKE deployments with Workload Identity.
ConfigFactory priority order:
1. GSM (when OCE_TENANT_GCP_PROJECT_ID is set)
2. File config (YAML files at conventional paths)
3. Environment variables (when {VENDOR_PREFIX}_{MODULENAME}_ENV_CONFIG=1)
4. Database globals (default)
Includes PHPStan-compliant null handling for GSM SDK responses.
b907b6c to
c3e9b68
Compare
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.
Adds abstracted GSM support to module template: