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

Simple auth formatting #478

Closed
AdamNuclear opened this issue Nov 23, 2023 · 3 comments · Fixed by #437
Closed

Simple auth formatting #478

AdamNuclear opened this issue Nov 23, 2023 · 3 comments · Fixed by #437
Assignees
Labels
Milestone

Comments

@AdamNuclear
Copy link

Issue: Various projects are consuming secrets in a specific format
Example: htpasswd in secret - any webserver is expecting:

apiVersion: v1
data:
  users: <b64 encoded key:value  list of users>

decoded b64:

user:htpassword

Would be good to have formatting options like:

kind: VaultStaticSecret
metadata:
  name: vault-kv-app
  namespace: app
spec:
  format: <string> | default (json) json/yaml/kv
  destination_key_name: <string> | default: data

optionally would be also great to have the possibility to select just keys from kv:

spec:
 keys:
 - 1secretkey
 - 2secretkey

This would make the secrets operator way more compatible with all the software around without rewriting/modifying other projects.

@AdamNuclear AdamNuclear added the enhancement New feature or request label Nov 23, 2023
@adrianmoisey
Copy link
Contributor

Would this issue be solved by #437 ?

@AdamNuclear
Copy link
Author

yea that would definitely solve it!

@benashz benashz added this to the v0.5.0 milestone Nov 24, 2023
@benashz benashz self-assigned this Feb 6, 2024
@benashz benashz linked a pull request Feb 7, 2024 that will close this issue
@benashz
Copy link
Collaborator

benashz commented Feb 7, 2024

Closed with #437

@benashz benashz closed this as completed Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants