Skip to content

chore: Bump version for automation-flavors#352 - #1895

Draft
rhacs-bot wants to merge 1 commit into
masterfrom
bump-automation-flavors-versions-pr-352
Draft

chore: Bump version for automation-flavors#352#1895
rhacs-bot wants to merge 1 commit into
masterfrom
bump-automation-flavors-versions-pr-352

Conversation

@rhacs-bot

Copy link
Copy Markdown
Contributor

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

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Review Change Stack

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: Pro Plus

Run ID: a1225f8d-464a-43fd-9ca0-6108a2016bee

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between c3d91a7 and efb3bf8.

πŸ“’ Files selected for processing (1)
  • chart/infra-server/Chart.yaml

πŸ“ Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated the automation flavor version used by chart deployment configuration.

Walkthrough

The infra-server Helm chart updates the automationFlavorsVersion annotation from 0.15.5 to 0.15.6.

Changes

Automation flavors version

Layer / File(s) Summary
Update chart annotation
chart/infra-server/Chart.yaml
The automationFlavorsVersion annotation changes from 0.15.5 to 0.15.6.

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

Suggested reviewers: bradlugo

πŸš₯ Pre-merge checks | βœ… 5
βœ… Passed checks (5 passed)
Check name Status Explanation
Title check βœ… Passed The title clearly identifies the version bump for automation-flavors pull request #352.
Description check βœ… Passed The description accurately describes the automation-flavors version bump and links it to pull request #352.
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-352

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

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

@rhacs-bot

Copy link
Copy Markdown
Contributor Author

A single node development cluster (infra-pr-1895) 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-1895 --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:

Or:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants