You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Review and discuss the secrets env features.
The text was updated successfully, but these errors were encountered:
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 becomedir1_secret1
variable name. If the dir was selected directly then it would just besecret1
. We could change this behaviour with a flag. This needs further discussion and spec.Additional context
Tasks
secrets env
features.The text was updated successfully, but these errors were encountered: