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

Auto-locate and inject matching secrets as needed #54

Closed
Tracked by #111
aaronsteers opened this issue Feb 21, 2024 · 1 comment · Fixed by #143
Closed
Tracked by #111

Auto-locate and inject matching secrets as needed #54

aaronsteers opened this issue Feb 21, 2024 · 1 comment · Fixed by #143
Assignees

Comments

@aaronsteers
Copy link
Contributor

Originally tracked in #1

Secrets management Phase 2. Auto-detect and inject

In this phase, presumably we'd be able to auto-inject secrets if they match a specific naming convention that aligns with the source name and setting name.

Tech Spec here:

https://docs.google.com/document/d/1rqoRuGRDvSYX8TmtxvpJv-XJgzfN46fLYtuMymz-QE8/edit#heading=h.c4ztxwwo0ign

Re: Priority

We can probably postpone/deprioritize this one for a little while. It will be most valuable we want the same secret value to be applicable from both local and hosted execution models.

@bindipankhudi
Copy link
Contributor

To be done prior to #33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants