vmware / terraform-provider-vra

Terraform Provider for VMware Aria Automation
https://registry.terraform.io/providers/vmware/vra/
Mozilla Public License 2.0
104 stars 93 forks source link

Enhancement: Support for NSX Global Managers as of vRealize Automation 8.4.1 #351

Closed tenthirtyam closed 2 years ago

tenthirtyam commented 3 years ago

vRealize Automation Version

vRealize Automation 8.4.1

Terraform Version

1.0.0

terraform-provider-vra plugin version

0.3.7

Describe the Bug

As of vRealize Automation 8.4.1, per the release notes:

Support of NSX Federation with NSX-T Cloud Account (Global Manager / Local Manager, existing networks)

With an NSX-T cloud account, it is now possible to connect to NSX-T Global Manager and configure an association between NSX-T Global Manager and Local Managers in the context of the NSX-T Federation

To support this, the provider will need an enhancement to support the creation of NSX Manager cloud accounts that can be selected as the NSX Global Manager type and then perform the association with the NSX Local Manager cloud account and vCenter Server cloud account.

Something like the following:

resource "vra_cloud_account_nsxt" "this" {
  name = "sfo-w01-nsx-gm01"
  description = "NSX Global Manager for Workload Domain 01"
  username = "svc-vra-nsx@rainpole.io"
  password = "************************"
  hostname = "sfo-w01-nsx-gm01.rainpole.io"
  associated_cloud_account_ids = [vra_cloud_account_nsxt.this.id, vra_cloud_account_vsphere.this.id]
  accept_self_signed_cert = true
  tags {
    key    = "cloud"
    value = "private"
  }
}

Additional Context

See https://docs.vmware.com/en/vRealize-Automation/8.4/Using-and-Managing-Cloud-Assembly/GUID-9AC61682-75D5-4576-8BB9-E654156FA02E.html.

github-actions[bot] commented 3 years ago

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!

tenthirtyam commented 3 years ago

@Prativa20 or @frodenas - would you mind applying a label so this issue is not marked as stale or purged by the GitHub actions?

Thanks, Ryan