[ROSAENG-1452] Automating Managed Platform maintenance for ocm-agent-operator

[samanthajayasinghe]

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.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 1:32 AM UTC · Completed 1:35 AM UTC
Commit: 7f9e641 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Category: Feature — maintenance automation script
Severity: Low (developer tooling improvement, no production impact)

Problem

No automated maintenance script exists for ocm-agent-operator. Each OCP release maintenance cycle requires manual dependency updates and boilerplate validations, consuming team time.

Recommended Approach

Port the hack/maintenance-update.py script from managed-upgrade-operator and adapt it for this repo. The MUO script (~470 lines of Python) handles:

1. Updating version-pinned Go deps to an OCP release branch
2. Updating latest-tracking Go deps
3. Running go mod tidy and container-make validation
4. Updating boilerplate and re-validating
5. Interactive git staging and committing

Key adaptations needed:

• Update default --version-deps to match this operator's release-pinned dependencies
• Update default --latest-deps for this operator's latest-tracking dependencies
• Update the controller-runtime version mapping for supported OCP releases
• Add documentation to the repo describing the maintenance workflow

Per the issue's non-goal, release-specific dependency updates are out of scope — focus on existing deps and boilerplate validations.

Proposed Test Case

# 1. Run without --release flag (latest deps + boilerplate only)
python hack/maintenance-update.py
# Expect: updates latest deps, runs go mod tidy, validates, updates boilerplate

# 2. Run with --release flag
python hack/maintenance-update.py --release release-4.19
# Expect: updates version-pinned deps to release-4.19, updates controller-runtime, validates

# 3. Invalid release version
python hack/maintenance-update.py --release invalid-version
# Expect: non-zero exit with error message

# 4. Verify help output shows correct defaults
python hack/maintenance-update.py --help
# Expect: default deps listed are appropriate for ocm-agent-operator

---

Next steps:

• /fs-code — agent creates a PR to implement this issue
• /fs-code <your instruction> — agent implements with your specific guidance

[fullsend-ai-triage]

🤖 Triage · ❌ Terminated · Started 1:36 AM UTC · Ended 1:43 AM UTC
Commit: 7f9e641 · View workflow run →

[samanthajayasinghe]

/fs-code

[fullsend-ai-triage]

🤖 Finished Triage · ❌ Failure · Started 1:36 AM UTC · Completed 1:43 AM UTC
Commit: 7f9e641 · View workflow run →

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 1:44 AM UTC · Completed 1:53 AM UTC
Commit: 7f9e641 · View workflow run →

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 2:21 AM UTC · Completed 2:23 AM UTC
Commit: 7f9e641 · View workflow run →

[fullsend-ai-triage]

An implementation PR is already in flight that adds the hack/maintenance-update.py script ported from managed-upgrade-operator, adapted with ocm-agent-operator-specific dependency defaults, along with documentation updates in docs/development.md.

The PR is currently awaiting /ok-to-test from an org member before CI can run.

Addressed by:

• feat(#320): add maintenance automation script #321