Issue/Help with "Update infrastructure settings"

Documentation link

I am using the exact payload as required but the connector-connector-blocks and connector-application-blocks are not getting updated.

Describe the problem

Request payload -

{ "infrastructure_subnet": "10.250.20.0/24", "connector-connector-blocks": { "member": ["100.64.100.0/24"] }, "connector-application-blocks": { "member": ["10.250.10.0/24"] } }

Response payload -

{ "folder": "Shared", "infra_bgp_as": "65534", "infrastructure_subnet": "10.250.20.0/24", "tunnel_monitor_ip_address": "10.250.20.254", "captive_portal_redirect_ip_address": "10.250.20.254", "loopback_ips": [], "egress_ip_notification_url": { "msg": { "@status": "success", "@code": "19", "result": { "total-count": 1, "url": "" } } }, "api_key": "api_key", "connector_connector_blocks": {}, "connector_application_blocks": {} }

Suggested fix

Update the documentation or the backend code to ensure the connector-connector-blocks and connector-application-blocks gets populated.
Also please keep consistent variables naming convention i.e. either kebab-case (dash-case) or snake_case.

Locate the documentation for “Update infrastructure settings” and the request/response schema that defines these fields. Compare the documented names with the submitted payload and returned fields, then determine whether the correction belongs in the MDX documentation or backend behavior. Done means the naming and expected population of both connector block fields are unambiguous and verified.