Problem to import segment created by HCX in NSX in VMC about terraform-provider-nsxt HOT 4 CLOSED

Indeed my import works with an nsxt_policy_fixed_segment.
Many tanke for this info @salv-orlando

What are the differences between nsxt_policy_fixed_segment and nsxt_policy_segment?

from terraform-provider-nsxt.

Hello,

The search aggregate API query you reported does not specify the resource_type.
I might be wrong but I think the segment created by HCX are tier-1 segments.

Which resource or data source did you use?
Did you try using nsxt_policy_fixed_segment as well?

@annakhm moving this into your queue.

from terraform-provider-nsxt.

Hello,

I use nsxt_policy_segment in my case. I don't test nsxt_policy_fixed_segment.

My Code;
``resource "nsxt_policy_segment" "segments" {
lifecycle {
ignore_changes = [security_profile]
}

for_each = local.segments
display_name = each.key
description = each.value.description
connectivity_path = "/infra/tier-1s/cgw"
transport_zone_path = data.nsxt_policy_transport_zone.transport_zone.path

tag {
scope = each.value.env
tag = "env"
}
tag {
scope = each.value.app
tag = "app"
}
subnet {
cidr = each.value.subnet
}
advanced_config {
connectivity = "OFF"
}
}``

from terraform-provider-nsxt.

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.

from terraform-provider-nsxt.