annakhm

Hi @ajgrinnell, sorry for late response, I've missed this comment. Bridge support was added with version 3.2.9

I'm reopening this, however note that all LB APIs are deprecated on NSX. This is the reason these are not prioritized in dev.

Hi @martinrohrbach, unfortunately non-policy resources are not prioritized since these are deprecated on NSX. We are evaluating migration options from MP po Policy.

For the security policy, the issue is fixed with newly introduced pair of resources https://registry.terraform.io/providers/vmware/nsxt/latest/docs/resources/policy_parent_security_policy https://registry.terraform.io/providers/vmware/nsxt/latest/docs/resources/policy_security_policy_rule Those resources are still in Beta but expected to be promoted in next release....

Closing this as VPN support is now released

Hi @scharrier-revolve, if you create `nsxt_policy_fixed_segment` rather than `nsxt_policy_segment`, transport zone will not be mandated. Would this work for your scenario?

Hi @Suselz, segment data source was added https://github.com/vmware/terraform-provider-nsxt/pull/870 (not yet released), hence closing this.

Hello, sorry it took us long to respond to this issue, could you please help clarify it? The issue says `The target_type VirtualMachine is not supported` However group resource offers...

Please reopen with logs if reproduced, thank you!

Hi @scila1996, sorry for delay in response. Address bindings setting for segment is deprecated in NSX, address bindings for ports are used instead. If this relevant for your use case?