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
Ordering when pushing and pulling is not kept #26
Comments
Are you adding your secrets via the UI or using our old NodeJS CLI? |
I tried with both and in the UI we cannot reorder (except A->Z - Z->A). I am trying with the new CLI now, since i could not use it because of the email regex, that you have fixed. |
Ah i see, so you would like the ability to order your secrets and have them injected in that order? |
Yes exactly because I have some envs that depends on each other, example:
|
Oh i see, you would like to also reference environment variables created earlier. I'll let you know once we pick this task up. |
Good news, shell parameter expansion is now supported. It is on by default but you can turn it off with Don't forget to update your CLI first! Let me know if things are working for you. |
Excellent ! It is working. |
We have an issue in my team, when we add envs that depends on others, we need dependencies came after the source env, so sometime we reorder them, or even grouping them by microservice by adding comments (monorepo), but the order is absolutely not kept and same for comments. So each time we pull envs we have to reorder them and add comments.
To be honnest, commenting is not critical, but reordring each time the envs is really annoying.
The text was updated successfully, but these errors were encountered: