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
Which functionality do you think we should update/improve?
Deletion of objects should have a dry run capability, that allows user to find out what all will be deleted, if he runs deletion, without actually running it.
Something like maybe odo object delete --dry or odo object delete --dry-run
Why is this needed?
This should allow user to get information about what will be deleted without risk of actual deletion.
Also, this can possibly be integrated with machine readable output, to allow say adapters to find out what will be removed, inform user, take his ack and then delete with odo object delete -f
The text was updated successfully, but these errors were encountered:
mohammedzee1000
added
status/blocked
Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo)
priority/Low
Nice to have issue. It's not immediately on the project roadmap to get it done.
labels
Feb 12, 2019
currently as we ask for confirmation Are you sure you want to delete nodejs-nodejst-lmgk from app? (y/N) for most of the delete commands. I dont see a need for having a dry-run flag anymore.
cc @mohammedzee1000 .
Closing this for now
[kind/Enhancement]
Which functionality do you think we should update/improve?
Deletion of objects should have a dry run capability, that allows user to find out what all will be deleted, if he runs deletion, without actually running it.
Something like maybe
odo object delete --dry
orodo object delete --dry-run
Why is this needed?
This should allow user to get information about what will be deleted without risk of actual deletion.
Also, this can possibly be integrated with machine readable output, to allow say adapters to find out what will be removed, inform user, take his ack and then delete with
odo object delete -f
Relies on #804 Please wait for it to close
The text was updated successfully, but these errors were encountered: