annakhm
annakhm
Hi @bachmannmichael, if I may ask - with which version of NSX did you observe the bug in pagination for the `vifs` API? This may help with troubleshooting https://github.com/vmware/terraform-provider-nsxt/issues/787.
Thank you. According to https://kb.vmware.com/s/article/89437, this should be solved with NSX 3.2.2
Closing this as per https://github.com/vmware/terraform-provider-nsxt/pull/773 Thank you for you contribution @nvibert!
Hi @akhomyakov, I just double-checked, and env variables are working fine for me on linux. This is implemented via pretty basic functionality so its hard to imagine what could go...
Hi @scharrier-revolve, Did I understand correctly that this is an enhancement ask, not a bug? You would like to skip TZ configuration, but there is no functional issue with supplying...
Hi @bernd-reize, what version of NSX are you using? I don't seem to be able to reproduce the error you're seeing.
Thanks for responding. I still wasn't able to see this happening locally, so could you please provide debug logs (set TF_LOG="debug")
Hi @benzander, `remote_auth` is a vidm-specific setting that I believe is no longer required for NSX > 3.2. Its purpose it to set "Remote: " header. Is that the behavior...
If you don't mind I'll change the topic of this issue to reflect the fact that session-based auth is not yet supported for policy resources. We're waiting for SDK support...
Hi @sebastiangrugel, I notice that in your configuration same predefined policy seems to be used in two separate `nsxt_policy_predefined_security_policy` resources: `path = data.nsxt_policy_security_policy.policy-vmc-example.path` A single `nsxt_policy_predefined_security_policy` resource should be used...