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

Review and improve secrets env command design #296

Open
tegefaulkes opened this issue Oct 1, 2024 · 1 comment
Open

Review and improve secrets env command design #296

tegefaulkes opened this issue Oct 1, 2024 · 1 comment
Labels
development Standard development

Comments

@tegefaulkes
Copy link
Contributor

Specification

The functionality of the secrets env command needs to be evaluated. The current implementation doesn't quite match some people intuitive understanding along with some potential features being missing. We need to have a discussion on what should be included and how. What exactly is missing and what can be changed.

During a meeting we discussed how the directories and naming of the secrets would work. Currently selecting a directory, every secret within that directories tree is included in the output with the same name as the secret name. If there is a conflict the behaviour is decided by a CLI option.

It has been suggested that to avoid conflicts we append the directories name to the secret so dir1/secret1 would become dir1_secret1 variable name. If the dir was selected directly then it would just be secret1. We could change this behaviour with a flag. This needs further discussion and spec.

Additional context

Tasks

  1. Review and discuss the secrets env features.
@tegefaulkes tegefaulkes added the development Standard development label Oct 1, 2024
Copy link

linear bot commented Oct 1, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Standard development
Development

No branches or pull requests

1 participant