Closed AndriySidliarskiy closed 3 days ago
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale
. If you still need help, feel free to comment or reopen the issue!
What happened?
So now the secrets manager stores only value but we need also the store and key. Because not it`s not possible to store json data in Kubernetes secrets without encrypting this value.
How can we reproduce it?
What environment did it happen in?