You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The provider includes two resources to manage firewall rules: "nsxt_policy_security_policy" where rules and policy form a compound resource, and "nsxt_policy_security_policy_rule" to manage rules as objects separate from the policy.
Both these resources only accept a list of paths as input to services parameter of a rule.
Describe the solution you'd like
We would like to have an extra input for when we need to create a firewall rule on protocols and ports, rather than policy services.
The NSXT API offers a way to do that by including the parameter "service_entries" in the POST/PUT/PATCH request body as below :
Is your feature request related to a problem? Please describe.
The provider includes two resources to manage firewall rules: "nsxt_policy_security_policy" where rules and policy form a compound resource, and "nsxt_policy_security_policy_rule" to manage rules as objects separate from the policy.
Both these resources only accept a list of paths as input to services parameter of a rule.
Describe the solution you'd like
We would like to have an extra input for when we need to create a firewall rule on protocols and ports, rather than policy services.
The NSXT API offers a way to do that by including the parameter "service_entries" in the POST/PUT/PATCH request body as below :
{ ... "service_entries": [ { "l4_protocol": "TCP", "source_ports": [ "22-3300" ], "destination_ports": [ "22" ], "resource_type": "L4PortSetServiceEntry", "marked_for_delete": false, "overridden": false, "_protection": "NOT_PROTECTED" } ... ],
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: