Rename ABI-specific baremetal vars to AGENT_BAREMETAL_* prefix#97
Rename ABI-specific baremetal vars to AGENT_BAREMETAL_* prefix#97fonta-rh wants to merge 2 commits into
Conversation
Align with dev-scripts PR #1922 naming convention: ABI-specific vars use the AGENT_ prefix to distinguish them from platform-level vars. Renamed: - BAREMETAL_IPS → AGENT_BAREMETAL_IPS - BAREMETAL_ISO_SERVER → AGENT_BAREMETAL_ISO_SERVER - BAREMETAL_MACS → AGENT_BAREMETAL_MACS Kept as-is (platform-level, used by both IPI and ABI in network.sh): - BAREMETAL_API_VIP - BAREMETAL_INGRESS_VIP Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fonta-rh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
WalkthroughThe baremetal configuration generator now exports agent-prefixed IP, MAC, and ISO server variables, while the sample inventory documents the updated MAC export name and existing validation and network exports remain unchanged. ChangesBaremetal agent export updates
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 10 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (10 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 `@deploy/openshift-clusters/scripts/baremetal-adopt.sh`:
- Around line 435-439: Rename the newly introduced shell locals in the baremetal
adoption logic to uppercase names: change ip_list to IP_LIST, mac_list to
MAC_LIST, and the loop index i to INDEX. Update every reference across both
affected loops, including array indexing and accumulation, without changing the
existing behavior.
- Around line 453-460: Update
deploy/openshift-clusters/inventory_baremetal.ini.sample so its data_mac
documentation references AGENT_BAREMETAL_MACS instead of BAREMETAL_MACS,
matching the export emitted by baremetal-adopt.sh.
🪄 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: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: 9d7c95bb-2477-47c1-ad2a-8bf4472ece08
📒 Files selected for processing (1)
deploy/openshift-clusters/scripts/baremetal-adopt.sh
The data_mac doc comment still referenced the old BAREMETAL_MACS name. Co-Authored-By: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
BAREMETAL_IPS→AGENT_BAREMETAL_IPS,BAREMETAL_ISO_SERVER→AGENT_BAREMETAL_ISO_SERVER,BAREMETAL_MACS→AGENT_BAREMETAL_MACSinbaremetal-adopt.shBAREMETAL_API_VIPandBAREMETAL_INGRESS_VIPas-is (platform-level, used by both IPI and ABI innetwork.sh)Why
Aligns with dev-scripts#1922 naming convention. dtantsur's review requested that ABI-specific config vars use the
AGENT_prefix to distinguish them from platform-level vars. The rename was applied in dev-scripts; this PR updates the generator side.Dependency chain
This PR must merge before dev-scripts#1922 — otherwise the generated config file uses old names that dev-scripts no longer reads.
/hold
Test plan
make shellcheckpassesmake baremetal-adoptgeneratesconfig_baremetal_fencing.shwithAGENT_BAREMETAL_*var names🤖 Generated with Claude Code
Summary by CodeRabbit