Skip to content

Update automationFlavorsVersion to snapshot version#1866

Draft
porridge wants to merge 9 commits into
masterfrom
porridge-af-pr-348
Draft

Update automationFlavorsVersion to snapshot version#1866
porridge wants to merge 9 commits into
masterfrom
porridge-af-pr-348

Conversation

@porridge

Copy link
Copy Markdown
Contributor

No description provided.

@coderabbitai

coderabbitai Bot commented Jun 22, 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: Enterprise

Run ID: d94baf11-bbec-4c20-a6fc-6496256800e1

📥 Commits

Reviewing files that changed from the base of the PR and between 7be4065 and 8259f9d.

📒 Files selected for processing (1)
  • chart/infra-server/Chart.yaml
✅ Files skipped from review due to trivial changes (1)
  • chart/infra-server/Chart.yaml

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated the deployed chart metadata to reference a newer snapshot build version (automationFlavorsVersion).

Walkthrough

The Helm chart metadata for infra-server updates automationFlavorsVersion from 0.15.2 to 0.15.1-16-ge50baf7cad-snapshot.

Changes

Helm chart metadata update

Layer / File(s) Summary
Version field update
chart/infra-server/Chart.yaml
automationFlavorsVersion is updated from 0.15.2 to 0.15.1-16-ge50baf7cad-snapshot.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive No pull request description was provided, so relatedness to the changeset cannot be assessed. Add a brief description of the change and its intent, such as updating automationFlavorsVersion to a snapshot build.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updating automationFlavorsVersion to a snapshot version.
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 porridge-af-pr-348

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

@rhacs-bot

Copy link
Copy Markdown
Contributor

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

@porridge porridge closed this Jun 26, 2026
@porridge porridge reopened this Jun 26, 2026
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.

2 participants