chore: Bump version for automation-flavors#351

[rhacs-bot]

Auto-generated: Bump automation-flavors version for https://github.com/stackrox/automation-flavors/pull/351.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 56ee1275-dfa8-4015-965a-53fb859f49d1

📥 Commits

Reviewing files that changed from the base of the PR and between 9da3234 and c1839bd.

📒 Files selected for processing (4)

• chart/infra-server/Chart.yaml
• chart/infra-server/static/janitor-delete-openshift-4.yaml
• chart/infra-server/static/workflow-openshift-4.yaml
• chart/infra-server/templates/openshift-4/secrets.yaml

🚧 Files skipped from review as they are similar to previous changes (2)

• chart/infra-server/Chart.yaml
• chart/infra-server/templates/openshift-4/secrets.yaml

---

📝 Walkthrough

Summary by CodeRabbit

• Improvements
  • OpenShift cleanup workflows now support secure authentication through a configured cluster manager API token.
  • Added managed secret configuration for storing and providing the cluster manager token to cleanup operations.
  • Updated the infrastructure chart to use the latest automation-flavors snapshot version.

Walkthrough

The Helm chart adds an OpenShift cluster manager API token Secret, injects it into destroy workflow containers, and updates automationFlavorsVersion to a snapshot version.

Changes

OpenShift token wiring

Layer / File(s)	Summary
Provision and inject cluster manager token chart/infra-server/templates/openshift-4/secrets.yaml, chart/infra-server/static/workflow-openshift-4.yaml, chart/infra-server/static/janitor-delete-openshift-4.yaml	Adds the token Secret and references it from the OpenShift destroy containers.

Chart metadata

Layer / File(s)	Summary
Update chart version metadata chart/infra-server/Chart.yaml	Changes automationFlavorsVersion to the new snapshot version.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: stehessel

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly reflects the main change: bumping the automation-flavors version.
Description check	✅ Passed	The description is directly related to the changeset and states the automation-flavors version bump.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-automation-flavors-versions-pr-351

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[rhacs-bot]

A single node development cluster (infra-pr-1887) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1887 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🔓 You must go to to export an . Your token from the prod infra instance will not work with dev environments.

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@chart/infra-server/static/workflow-openshift-4.yaml`:
- Around line 121-125: Add OPENSHIFT_CLUSTER_MANAGER_API_TOKEN to the main
workflow’s destroy container environment, using the same secretKeyRef name
openshift-cluster-manager-token and key OPENSHIFT_CLUSTER_MANAGER_API_TOKEN
already used by create. Keep the existing destroy environment entries unchanged.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 7c879648-b5d4-4a46-8290-bc2a27dfbbff

📥 Commits

Reviewing files that changed from the base of the PR and between e9ee222 and 9da3234.

📒 Files selected for processing (3)

• chart/infra-server/static/janitor-delete-openshift-4.yaml
• chart/infra-server/static/workflow-openshift-4.yaml
• chart/infra-server/templates/openshift-4/secrets.yaml