chore: Bump version for automation-flavors#350

[rhacs-bot]

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

[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: bf9cf840-30f3-4169-bc4e-30d43db379fe

📥 Commits

Reviewing files that changed from the base of the PR and between 5c7a410 and fa34b2f.

📒 Files selected for processing (1)

• chart/infra-server/Chart.yaml

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated the packaged release metadata to point to a newer snapshot build of a bundled component.

Walkthrough

Updates the automationFlavorsVersion field in the Helm chart metadata file to a snapshot/build-specific version string.

Changes

Chart Metadata Update

Layer / File(s)	Summary
Update automationFlavorsVersion chart/infra-server/Chart.yaml	Changes automationFlavorsVersion from 0.15.2 to 0.15.2-1-g424f20d5ec-snapshot.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested labels: chart, dependencies

Suggested reviewers: None identified from the diff.

Poem:
A single line, a version's tweak,
From plain release to snapshot streak,
No logic bent, no code astray,
Just one small hop along the way. 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: bumping the automation-flavors version.
Description check	✅ Passed	The description is directly related to the version bump and upstream automation-flavors PR.
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-350

---

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-1874) 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-1874 --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