feat: show detailed NetworkManager connection diffs in check mode - #918
Conversation
|
CI tests do not run automatically on pull requests. A role repository See GitHub CI testing using /citest Run every available CI workflow: Run the linting and other lightweight checks: Run the integration tests (QEMU/container and Testing Farm): Run one or more selected workflows by separating their names with spaces:
Post another |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: linux-system-roles/network/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review. 📝 WalkthroughWalkthroughNetworkManager check-mode output now reports connection property and collection differences, with secret values redacted. Unit tests and a provider playbook cover diff formatting, dry-run logging, and whether previewing changes alters the live profile. ChangesNetworkManager check-mode connection diffs
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to The check-mode diff is ordered correctly, and the provider test checks that previewing changes leaves the live connection unchanged. No identified issue prevents merging after normal checks. 🚥 Pre-merge checks | ✅ 4 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (4 passed)
Full details: Description FormatExplanation The PR description contains the required
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
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 |
|
/citest all |
1 similar comment
|
/citest all |
Report individual route, address and DNS changes, scalar old and new values, and added or removed settings through the existing stderr logger. Use libnm setting diffs with the same normalization and comparison flags as connection comparison, while redacting credentials and private keys. Signed-off-by: Josephine Pfeiffer <josie@redhat.com>
Exercise property diffs with real libnm objects, including populated settings, route attributes, secret redaction and older libnm APIs. Verify check-mode logging and that dry runs do not update connections. Signed-off-by: Josephine Pfeiffer <josie@redhat.com>
Run the role through Ansible to verify detailed IPv4 and IPv6 diffs, unchanged connections during check mode, and convergence after applying. Check that the test profile and interface are removed during cleanup. Signed-off-by: Josephine Pfeiffer <josie@redhat.com>
1112e25 to
a6b15bd
Compare
|
/citest all |
|
/citest tft |
|
lgtm - would like Sergei to take a look |
Enhancement:
Add detailed NetworkManager connection diffs to the network role’s check-mode output.
Reason:
Reporting only “is-modified” does not provide enough detail for change control, especially across large deployments.
Result:
Check mode reports individual route, address, and DNS additions/removals, scalar changes with old and new values, and added/removed settings.
Issue Tracker Tickets (Jira or BZ if any):
https://redhat.atlassian.net/browse/NMT-2408
Summary by CodeRabbit
ansible-playbookoutput, including added or removed settings and properties, collection changes, and old and new values. Secret values are redacted, and--diffis not required.