Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Add support to specify existing secretStore for external secrets #2903

Closed
2 tasks done
pawan-mehta-dt opened this issue Jan 27, 2023 · 0 comments · Fixed by #2899
Closed
2 tasks done

Feature: Add support to specify existing secretStore for external secrets #2903

pawan-mehta-dt opened this issue Jan 27, 2023 · 0 comments · Fixed by #2899
Assignees

Comments

@pawan-mehta-dt
Copy link
Contributor

🔖 Feature description

Add support to specify existing secretStore for external secrets
Also, make property field optional in esoData as all secrets are not in key-value pair format

🎤 Pitch

I have created ClusterSecretStore and I want to refer the same in my external secrets but I am not able to do so.

✌️ Solution

Allow some fields to accept existing secretstore created outside app to be referred in external secrets

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

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 a pull request may close this issue.

4 participants