feat: support writing file contents directly from SPC not in secret manager #174
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.
A possible implementation/fix for:
kubernetes-sigs/secrets-store-csi-driver#948
This would allow the GCP secret provider class to write some static
non-secret data to a file next to the actual secret. This type of
behavior is needed because some systems like ArgoCD take in all
configuration from a single K8s secret with different key/values.
This could also be used to put public keys (and keep the private key
as just the secret value).