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 resource "nsxt_policy_intrusion_service_policy" only supports distributed IDPS policies and to apply IDPS rules to the distributed firewall (DFW) or to more specific security groups (using the "scope" argument). I need to be able to create intrusion service policies (and rules) that get applied to a T1 gateway.
Describe the solution you'd like
As already possible for firewall policies ("nsxt_policy_security_policy" and "nsxt_policy_gateway_policy") I have to be able to configure ditributed intrusion service policies as well as gateway intrusion service policies by using different resource types, e.g. "nsxt_policy_intrusion_service_policy" for dIDPS and "nsxt_policy_gateway_intrusion_service_policy" for gwIDPS on T1 gateways.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The resource "nsxt_policy_intrusion_service_policy" only supports distributed IDPS policies and to apply IDPS rules to the distributed firewall (DFW) or to more specific security groups (using the "scope" argument). I need to be able to create intrusion service policies (and rules) that get applied to a T1 gateway.
Describe the solution you'd like
As already possible for firewall policies ("nsxt_policy_security_policy" and "nsxt_policy_gateway_policy") I have to be able to configure ditributed intrusion service policies as well as gateway intrusion service policies by using different resource types, e.g. "nsxt_policy_intrusion_service_policy" for dIDPS and "nsxt_policy_gateway_intrusion_service_policy" for gwIDPS on T1 gateways.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: