Fix RouterNodeConfigurationStatus FailedResources - missing L3VPN - #761
Fix RouterNodeConfigurationStatus FailedResources - missing L3VPN#761andreaskaris wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (8)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe change updates ChangesFailed resource enum support
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The PR consistently enables L3VPN failed-resource reporting across the API and deployed schemas, with no remaining merge-blocking risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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 |
Signed-off-by: Andreas Karis <ak.karis@gmail.com>
make generate && \ make manifests && \ make bumplicense && \ make generate-all-in-one && \ make bundle && \ make generate-all-ci Signed-off-by: Andreas Karis <ak.karis@gmail.com>
3582e48 to
0ba7cf6
Compare
Is this a BUG FIX or a FEATURE ?:
/kind bug
What this PR does / why we need it:
Fix RouterNodeConfigurationStatus FailedResources reporting - L3VPN was missing and it would show:
Special notes for your reviewer:
N/A
Release note:
AI Guidelines Acknowledgment:
Summary by CodeRabbit
New Features
L3VPNis now recognized as a valid failed resource type in router node configuration status.Documentation
L3VPNfailed resources.