Add support to configure external IP ranges from IPAM provider

[ksoul78]

vRA version 8.2 on prem Terraform version 0.13.4 terraform-provider-vra plugin version 0.3.3

Is your feature request related to a problem? Please describe. The objective is to configure the external ranges of the IPAM supplier by associating them with the fabric network.

Describe the solution you'd like

• Resource to add IPAM endpoint (Efficient IP) and associated data source with filter on name at least, see : adding cloud assembly Integration resources
• Data source to get external ip range by name, ipam zone , and endpoint id
• Resource to create an external ip range that associate external-network-ip-ranges id to fabricNetworkId

Describe alternatives you've considered At the moment we did it through :

• Cloud Assembly UI to create IPAM endpoints and get their IDs (missing API call ?)
• vRO to create Network and IPAM Range association via API

Here the steps followed to configure an association via API calls:

1. Get fabric-networks (vSphere) by name and cloud account

   GET /iaas/api/fabric-networks?$filter=name+eq+'V0001_FABRIC_NETWORK_NAME' and cloudAccountIds.item+eq+'45d13an1-4523-6412-8796-13d43k15d612'

2. Get external IP range by name, zone ipam, and endpoint id

   GET iaas/api/external-network-ip-ranges?$filter=addressSpaceId+eq+'myCompany' and name+eq+'V0001_VLAN_NAME' and (endpointLinks.item eq /resources/endpoints/12345678-1234-1234-1234-123456456012')

3. Associate both objects by updating External IP object with the fabricNetworkId Update external ip object with the fabricNetworkId

   PATCH /iaas/api/external-network-ip-ranges/{id}

   {
   "fabricNetworkId": "12345678-0000-aaaa-2222-1a2ba3c95de"
   }

Additional context

• We are using 2 IPAM Endpoints (due to a vRA8 limitation for now) : 1 per Cloud Account (but pointing in reality to same IPAM cluster)

[github-actions[bot]]

Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[dimatha]

Hello guys, any chances/plans to work on this one ?

[github-actions[bot]]

Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!