Open fa-elepape opened 6 months ago
For now I've applied a quick workaround using this patch:
--- plugins/module_utils/common.py 2024-02-22 12:02:42.000000000 +0530
+++ plugins/module_utils/common.py 2024-02-22 12:02:42.000000000 +0530
@@ -59,7 +59,14 @@
get_args["cipheraliasname"] = get_args["ciphername"]
del get_args["ciphername"]
- if resource_name.endswith("_binding"):
+ if resource_name in {'responderglobal_responderpolicy_binding'}:
+ status_code, response_body = client.get(
+ resource=resource_name,
+ id=resource_id,
+ args={'type': get_args.pop('type')},
+ filter=get_args,
+ )
+ elif resource_name.endswith("_binding"):
# binding resources require `filter` instead of `args` to uniquely identify a resource
status_code, response_body = client.get(
resource=resource_name,
Hi,
Could be related to this issue https://github.com/netscaler/ansible-collection-netscaleradc/issues/446 since the priority filter does not seem to work properly.
Summary
The
responderglobal_responderpolicy_binding
takes bothargs
andfilter
parameters in order to properly manage elements.GET requests take both
args
for thetype
andfilter
for the rest. DELETE requests take only theargs
parameter.As a side note, it appears the DELETE method doesn't care about the
priority
argument which leads to multiple bindings of the same policy at different priorities to all get deleted.Issue Type
Bug Report
Component Name
responderglobal_responderpolicy_binding
Python Version
Ansible Version
Ansible Configuration
netscaler.adc Collection Version
Target NetScaler Version
Equivalent NetScaler CLI Command
Steps to Reproduce
Expected Results
The
state: present
should not report changes when there are none. Thestate: absent
should work.Actual Results
Additioinal Notes
While the parameters deviate from the general case of the
_binding
resource, it appears to be properly documented in the NITRO API documentation.