fix: use new property format for port group playbook - #2595
Conversation
It has been noticed in `2026.1` deployments that the playbook for adding new port groups will fail as the properties returned are no longer uppercase and use spaces instead they are now lowercase with underscores. Signed-off-by: Jack Hodgkiss <jack@stackhpc.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (4)
🧰 Additional context used🪛 Checkov (3.3.13)etc/kayobe/environments/baremetal/ansible/add-port-groups.yml[low] 41-133: Ensure block is handling task errors properly (CKV2_ANSIBLE_3) 🔇 Additional comments (2)
📝 SummaryUpdates the WalkthroughThe ChangesPort group query correction
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to The playbook correction is narrowly scoped and should restore port-group creation for 2026.1 deployments. 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
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. Comment |
It has been noticed in
2026.1deployments that the playbook for adding new port groups will fail as the properties returned are no longer uppercase and use spaces instead they are now lowercase with underscores.