openshift / openshift/ocm-agent-operator
[ROSAENG-1452] Automating Managed Platform maintenance for ocm-agent-operator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 59
- Avg merge
- 10h 17m
- Merged PRs (30d)
- 25
Description
Summary
In this ticket, we'll want to optimize some of the maintenance work for ocm-agent-operator such that the amount of time spent by the team is reduced and the maintenance task for the operator is streamlined.
We can re-use the script that's used for MUO script https://github.com/openshift/managed-upgrade-operator/blob/master/hack/maintenance-update.py
ACCEPTANCE CRITERIA:
Automate maintenance for ocm-agent-operator to be able to easily handle maintenance per OCP release with minimum effort in a standardized way.
Operator repo docs are updated accordingly
NON GOAL:
We are not to update the deps specific to a OpenShift release yet. That will be done separately. For now, it's only about updating the existing deps and having boilerplate validations.
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 reading hack/maintenance-update.py in the managed-upgrade-operator repository and inspect the ocm-agent-operator repository's existing maintenance and dependency documentation. Done means a standardized automation workflow handles existing dependency updates and boilerplate validations for the operator, with the repository documentation updated; OpenShift-release-specific dependency updates remain out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100