-
Notifications
You must be signed in to change notification settings - Fork 12
Feature/check keys in parent prefix selector #295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testes locally and works nice! I like the new thorough tests and the nice error message. Just 2 minor changes
Co-authored-by: Fabian <30692464+faebr@users.noreply.github.com>
tests/e2e/Prefix/IPv4/prefixclaim-ipv4-invalid-parentprefixselector/chainsaw-test.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a small question for my understanding but looks good to me :)
* check if custom fields in parent prefix selector exist * add unit tests * add chainsaw test --------- Co-authored-by: Fabian <30692464+faebr@users.noreply.github.com>
With this feature a check is added to only allow existing fields in the parentPrefixSelector.
If the parent prefix selector contains a key for a custom field that does not exist in NetBox, the key is ignored in the filter.