-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem to import segment created by HCX in NSX in VMC #1110
Comments
Hello, The search aggregate API query you reported does not specify the resource_type. Which resource or data source did you use? @annakhm moving this into your queue. |
Hello, I use nsxt_policy_segment in my case. I don't test nsxt_policy_fixed_segment. My Code; for_each = local.segments tag { |
Indeed my import works with an nsxt_policy_fixed_segment. What are the differences between nsxt_policy_fixed_segment and nsxt_policy_segment? |
Hi @gmoulard, segment and fixed segment are different API endpoints in NSX, fixed segment is always attached to a gateway, while regular segment can be detached. Other than that, those segments are very similar. |
Describe the bug
hi,
When I create a segment in my VMC's NSX, I can import it into my tfstate.
Unfortunly when the segment is created by HCX, in my VMC's NSX, I can not import it on my tfstate.
The requeted API by provider « GET /policy/api/v1/infra/segments » don't find the segment !!!
And yet, the segement is visible in NSX consol and in NSX API "POST /policy/api/v1/search/aggregate?page_size=50&cursor=0&sort_by=display_name&sort_ascending=true"
In // I have an SR opened with vmware support on the same problem SR 24491732101
Best regard,
Guillaume
Reproduction steps
Expected behavior
import segment rec-test in nsxt_policy_segment.segments["rec-test"
Additional context
No response
The text was updated successfully, but these errors were encountered: