nsxt route_aggregation on a separate resource

[frederic-urban]

Is your feature request related to a problem? Please describe.

We would like to deploy VIP networks on our NSX Load Balancers (hosted on a T1). For some usage, we need to have some /32 IPs available on the T1 so we plan to broadcast a /29 using route aggregation on the T0 for physical network to know that the VIP network is behind our edge.

Each VIP Network could be associated to dedicated T1 LB and each T1LB comes with a dedicated terraform deployement for scalability.

Since the route aggregation configuration is in the t0 ressource, we are not able to scale as wanted.

Describe the solution you'd like

Is it's possible to create a "route_aggregation" ressource linked to t0 bgp configuration which create a entry held in the state of the deployement.

Then when a deployement is destroyed, the aggregation leave NSX aswell but all others deployement remain operationnal.

Describe alternatives you've considered

We could handle the route aggregation in another state and link the new Tier1 to the Tier0 using a data, but it needs to manipulate 2 separated terraform states

Additional context

We are in NSX 3.1 moving soon to 3.2 but i don't think this is usefull to solve the problem described above

[annakhm]

Unfortunately, route aggregations under bgp config are not managed as objects under a separate API, but rather as a list under BGP config object. Exposing those types of structures as separate resources in terraform in not best practice, as it causes concurrency issues (since the terraform resources that are created in parallel de-facto end up being part of the same list in single BGP object on NSX).

Have you considered using dynamic block for route aggregations, as part of nsxt_policy_bgp_config resource?

[salv-orlando]

Moving to 3.9.0 as we are close to the 3.8.0 release