Open Nacymus opened 4 months ago
Thanks for reporting!
Hello @annakhm ,
The fix that closed the issue resloved one part of the problem : reading SNI conf of the distant virtual server. Still, whan configuring SNI in Tf configurations, we see a permanent diff and the distant virtual server is not once updated.
Hi @Nacymus, in my local testing I don't observe this problem - snis are updated successfully.
Could you please provide your apply logs with TF_LOG="debug"
and TF_LOG_PROVIDER_NSX_HTTP="debug"
? That would help a lot with troubleshooting. Thank you!
Describe the bug
I am using nsxt_policy_lb_virtual_server with the ssl_client sni_paths attribute. The SSL Client configuration of the Virtual server is as follows:
When planning for the 1st time, I see changes on the sni_paths of my Virtual Server:
On apply, I see that one resource has been updated as stated in the plan:
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
But this change does not appear on the remote Virtual Server, And the applied changes are not replicated on the state either, so on the next plan, terraform evaluated exactly the same changes as on the 1st plan.
The plugin logs show the following warning :
Reproduction steps
Expected behavior
Applied changes on the SNI part of Client SSL config in Virtual server should be applied on the remote NSX-T resource
Additional context
No response