redhat-developer / redhat-developer/vscode-openshift-tools
Clarify what is expected of the user after they are provided YAML in "Create Service" workflow
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
It's not apparent what is expected of the user if they use the "Create Service" workflow and are presented with the YAML.
They are expected to apply this YAML to the cluster, either through the "Create" CodeLens, the "OpenShift: Create" command, or using the cli (kubectl create -f FILENAME).
It would be nice to explain this to the user, either in the notification popup when they are presented with the YAML, or maybe in a new step in the wizard before they are presented with the YAML.
See discussion in https://github.com/redhat-developer/vscode-openshift-tools/pull/3508#pullrequestreview-1710831497
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 by reviewing the "Create Service" workflow and the discussion in pull request #3508. Trace where the YAML is presented and decide whether the guidance belongs in the notification popup or a wizard step. Done means users are told how to apply the YAML through the Create CodeLens, the OpenShift: Create command, or kubectl create -f.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript, vscode
- Domain
- cloud, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100