allowing CIDRs, wildcards and Plural in IP and DNS#806
Conversation
Signed-off-by: entlein <einentlein@gmail.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (24)
✨ Finishing Touches🧪 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 |
Overview
network-wildcards: DNS leading/trailing/mid + CIDR + IPAddresses + "*" sentinel
Additional Information
CEL
networkneighborhoodhelpers now queryprojected fields with wildcard/CIDR/DNS-wildcard support and the v0.0.2
spec semantics (port/protocol checks degrade to address-only in v1
when only a CIDR is declared).
*(RFC 4592 single-label wildcard)*(subdomain-prefix wildcard)⋯(interior dynamic segment)*any-IP sentinelIPAddresseslist (deprecated single-IP field) preserved on thedecode path
How to Test
20 declarative fixture YAMLs under
tests/resources/network-wildcards/pin the wildcard contract end-to-end:
*any-IP and*as CIDRIPAddressesfield path⋯, trailing-**rejection⋯Has sister PR in storage