redhat-developer / redhat-developer/web-terminal-operator
WTO tooling image used is very old
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 42
- Forks
- 24
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 1
Description
The web terminal tooling image used in the clusterserviceversion of WTO (quay.io/wto/web-terminal-tooling:latest) is 3 years old.
We should either update the image used by default to be quay.io/wto/web-terminal-tooling:next or update the CI action for the WTO tooling repo to also push to quay.io/wto/web-terminal-tooling:latest. I'm leaning towards the former option, as there doesn't seem to be an official "release" action for WTO tooling: we just create a version tag and consume from that tag downstream.
Contributor guide
No contributing guide indexed for this repository
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 manifests/web-terminal.clusterserviceversion.yaml at the referenced tooling image and compare it with .github/workflows/next-build.yml in the WTO tooling repository. Decide between consuming the next tag or publishing latest, then verify the default image reference matches the chosen release flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100