Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dry run option for odo delete #1318

Closed
mohammedzee1000 opened this issue Feb 12, 2019 · 2 comments
Closed

Dry run option for odo delete #1318

mohammedzee1000 opened this issue Feb 12, 2019 · 2 comments
Labels
priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@mohammedzee1000
Copy link
Contributor

[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 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

Relies on #804 Please wait for it to close

@mohammedzee1000 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
@mohammedzee1000
Copy link
Contributor Author

/shrug

@mohammedzee1000 mohammedzee1000 removed the status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo) label Mar 29, 2019
@girishramnani
Copy link
Contributor

girishramnani commented Jan 2, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
None yet
Development

No branches or pull requests

3 participants