Closed thoresuenert closed 3 years ago
What about first fetching the contents of the .env
file (with get:env
), saving that to a file (or in memory), altering it, and using update:env
to replace the entire .env
file?
I feel like adding something like --overwrites
would muddy up this package, which is effectively just a CLI for the API.
When you use forge-cli in ci/cd pipelines for deployment of review apps its hard to update the env file accordingly in shell land.
We come up with an idea to provider overwrites to command as follows:
Which will grab the env file an overwrite the given variables.