Netbox custom field related object filter #1423
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue
Not tracked
New Behavior
Support for extra parameter "related_objet_filter" allowing to set a filter for related object, allowed when type=object
Filter is passed as a dict in the task:
Contrast to Current Behavior
This parameter wasn't supported
Discussion: Benefits and Drawbacks
I've noticed the reset of this param on the target objet must be done by passing an empty dict like "{{ {} }}". Setting it to null seems to be ignored by the API.
Like other data-dependent parameters, we rely on the remote API for asserting we can or connot use this paramater (this param is only allowed for type=object for instance)
Changes to the Documentation
Should be transparent
Proposed Release Note Entry
See fragment
Double Check
devel
branch.