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
I'm hoping this fits in the scope of this cmd line tool.
It would be helpful to have capability to send my local environment .env file to my project and have it save all the variables defined. This way when developing locally, I can get my environment defined in a file which is easier to work with then having to enter in fields that hide values once saved. Then I can simply send it to a project and have variables created or updated. This would also be beneficial for reference when building out tools to automate rolling credentials.
I did build out this functionality already on my fork so if it is of any interest, I can clean it up and submit a pull request.
The text was updated successfully, but these errors were encountered:
Hey @drollinger. There's some work going on around env handling (see #179). The feature you've implemented in your fork is definitely interesting. if you are still up for it, you are welcome to submit a pull request!
I'm hoping this fits in the scope of this cmd line tool.
It would be helpful to have capability to send my local environment .env file to my project and have it save all the variables defined. This way when developing locally, I can get my environment defined in a file which is easier to work with then having to enter in fields that hide values once saved. Then I can simply send it to a project and have variables created or updated. This would also be beneficial for reference when building out tools to automate rolling credentials.
I did build out this functionality already on my fork so if it is of any interest, I can clean it up and submit a pull request.
The text was updated successfully, but these errors were encountered: