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
Right now when running data clean I am asked to type in CLEAN DATA regardless of which environment I am targeting. My particular workflow is just typing a few letters in the console like pos-cli data and then browsing the history of previous commands. It may result in picking an invalid environment due to oversight. I try to double-check that each time, but sooner or later I’ll mess up and erase production :(
Actual behavior
[16:05:36]
[16:05:36] WARNING!!! You are going to REMOVE your data from instance: https://qa-golfstix.staging.oregon.platform-os.com/
[16:05:36] There is no coming back.
[16:05:36]
✔ If you still want to continue please type: 'CLEAN DATA' … CLEAN DATA
Expected behavior
A more meaningful test would ask you to enter the name of the environment you want to clean so
[16:05:36]
[16:05:36] WARNING!!! You are going to REMOVE your data from instance: https://qa-golfstix.staging.oregon.platform-os.com/
[16:05:36] There is no coming back.
[16:05:36]
✔ If you still want to continue please type name of the environment: 'qa' … qa
This way you make running data clean on the wrong instance harder.
Version
pos-cli: 4.4.11
node: v13.6.0
os: osx
The text was updated successfully, but these errors were encountered:
Right now when running data clean I am asked to type in
CLEAN DATA
regardless of which environment I am targeting. My particular workflow is just typing a few letters in the console likepos-cli data
and then browsing the history of previous commands. It may result in picking an invalid environment due to oversight. I try to double-check that each time, but sooner or later I’ll mess up and erase production :(Actual behavior
Expected behavior
A more meaningful test would ask you to enter the name of the environment you want to clean so
This way you make running data clean on the wrong instance harder.
Version
The text was updated successfully, but these errors were encountered: