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
The -f (--force) is not intented to delete devfile.yaml or .odo.
There currently is no option to delete local files using odo cli.
This is not a bug but an intended feature.
/close
I've opened this as a new feature request #5997
Please note that there is no way for odo to know if, devfile.yaml was generated by another tool or was downloaded by the user manually. The new proposed command will simply delete all odo-related files and directories even if they were not created by odo. This needs to be used with care.
The -f (--force) is not intented to delete devfile.yaml or .odo.
There currently is no option to delete local files using odo cli.
This is not a bug but an intended feature.
/close
I've opened this as a new feature request #5997
Please note that there is no way for odo to know if, devfile.yaml was generated by another tool or was downloaded by the user manually. The new proposed command will simply delete all odo-related files and directories even if they were not created by odo. This needs to be used with care.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/kind bug
What versions of software are you using?
Operating System:
Win10Pro
Output of
odo version
:How did you run odo exactly?
odo init
odo delete component -f
Actual behavior
devfile.yaml
is still there and.odo
has filesExpected behavior
Cleanup should be done
Any logs, error output, etc?
The text was updated successfully, but these errors were encountered: