redhat-developer / redhat-developer/vscode-openshift-tools
Migrate the odo commands
Open
@msivasubramaniaan is already working on this.
Since Nov 27, 2025.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
The extension should figure out a workflow to have NO usage of the odo commands.
- registry / registry --details --devfile (Done: #4189)
- preference view / preference add registry / preference remove registry (Done: #3850)
- deploy (In progress: https://github.com/redhat-developer/vscode-openshift-tools/issues/4482) (@vrubezhny)
- delete component (https://github.com/redhat-developer/vscode-openshift-tools/pull/5772 by @msivasubramaniaan )
- dev (In progress: https://github.com/redhat-developer/vscode-openshift-tools/issues/4541)
- describe component (In Review: #5747 by @vrubezhny)
- logs (Done: https://github.com/redhat-developer/vscode-openshift-tools/issues/4396)
- list service / add binding (Restored list service: https://github.com/redhat-developer/vscode-openshift-tools/pull/6000 by @msivasubramaniaan)
- Migrate Service Binding functionality out of SBO (https://github.com/redhat-developer/vscode-openshift-tools/issues/4682)
- init (In Progress: #5788 by @vrubezhny)
- run (In progress: https://github.com/redhat-developer/vscode-openshift-tools/issues/5776 by @msivasubramaniaan )
- analyze (Done: #4344 by @msivasubramaniaan)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.