improve the keycloak version handling
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Over in https://github.com/rstudio/ptd/pull/2165#issuecomment-3128131404 @ian-flores recommended improving the version handling to restore keycloak_version_string in WorkloadClusterComponentConfig and use that to set the appropriate label inside keycloak/kustomization/deploy/kubernetes.yaml.
This issue is to track making that improvement so that we can have more streamlined upgrades of keycloak versions.
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 linked pull request comment and locating WorkloadClusterComponentConfig, then inspect keycloak/kustomization/deploy/kubernetes.yaml. Trace how the Keycloak version is currently represented and applied. Done means the version string is restored in the config and the deployment label uses it for streamlined upgrades.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authentication, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100