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

Secrets Management for Connections #21

Closed
dhercher opened this issue Jun 5, 2020 · 1 comment · Fixed by #865
Closed

Secrets Management for Connections #21

dhercher opened this issue Jun 5, 2020 · 1 comment · Fixed by #865
Assignees
Labels
priority: p1 High priority. Fix may be included in the next release. type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.

Comments

@dhercher
Copy link
Collaborator

dhercher commented Jun 5, 2020

A connection should be able to reference secrets stored in many different sources when needed. To accomplish this we will need to create some sort of standard for referencing and extracting secrets.

This could be in the form of a connection name:
ie. kms:path/to/key

Or fields in a connection could be named with a reference themselves:
ie.

"host": "127.0.0.1",
"user": "root",
"password": {"source": "kms", "name": "path/to/my_secret"}
}```
@dhercher dhercher added priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) Beta labels Jun 5, 2020
@dhercher dhercher self-assigned this Jun 5, 2020
@freedomofnet freedomofnet added priority: p1 High priority. Fix may be included in the next release. and removed Beta priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) labels Jan 8, 2021
@freedomofnet
Copy link
Collaborator

Post beta feature.

@freedomofnet freedomofnet added priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) and removed priority: p1 High priority. Fix may be included in the next release. labels Jan 15, 2021
@freedomofnet freedomofnet added the type: feature request 'Nice-to-have' improvement, new feature or different behavior or design. label Jul 14, 2021
@nehanene15 nehanene15 added priority: p1 High priority. Fix may be included in the next release. Release Next release candidate and removed priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) labels Jul 15, 2021
@nehanene15 nehanene15 removed the Release Next release candidate label Jan 6, 2022
@nehanene15 nehanene15 added priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) and removed priority: p1 High priority. Fix may be included in the next release. labels Jun 1, 2022
@nehanene15 nehanene15 added priority: p1 High priority. Fix may be included in the next release. and removed priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) labels Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 High priority. Fix may be included in the next release. type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.
Projects
None yet
4 participants