Prompt user if extant .env file would be overwritten by running env-init #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR replaces a TODO: with bash scripting that prompts the user to confirm that .env should be overwritten.
Testing
warden env-init test magento2
; assert that the.env
file is created as normal.env
filewarden env-init test magento2
again; when prompted, answern
; assert that the change you made previously is still in the filewarden env-init test magento2
again; when prompted, answery
; assert that the change you made previously is no longer therewarden env-init test magento2
again; when prompted, answer anything other thany
orn
; assert that you are asked to provide a valid answer