redhat-developer / redhat-developer/vscode-openshift-tools
Distinguish bundled and not bundled cli tools in tools.json configuration file
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
Right now src/tools.json file is used only to define bundled (packaged into extension .vsix file) cli tools like odo or oc.
Extension also calls OpenShif Local from Cluster Editor to help developer with provisioning a single node OpenShift cluster on local workstation, but it is not bundled and has to be downloaded manually.
To accelerate time of release Cluster Editor should also use src/tools.json to help developer downloading latest OpenShift local release verified to work smoothly with extension.
OpenShift Local then can be part of automated update for CLI tools to latest version.
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.
Research direction
Start with src/tools.json and trace the Cluster Editor path that invokes OpenShift Local. Determine how bundled CLI tools are represented and how the latest verified OpenShift Local release is selected or downloaded. Done means the configuration distinguishes bundled from non-bundled tools and OpenShift Local participates in the CLI update flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100