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
{{provider:path:key}}template syntax for referencing cloud secrets in lifecycle.yaml env blocksSupport AWS
{{aws:path:key}}and GCP{{gcp:path:key}}secret providersGenerate ExternalSecret CRs per service/webhook with cloud secret references
Modify pod specs to use secretKeyRef for secret-backed env vars
Add secretProviders configuration to
global_configfor provider settingsSupport secrets in github, docker deployment types and webhooks
Support nested JSON access with dot notation (e.g.,
{{aws:config:database.password}})Build-time secrets supported in native build with buildkit engine via envFrom mounting in build containers
fixes envLens log streaming
Note: helm type service don't yet support this.