Terraform VCD 3.6.0 NSX-T VDC group and Distributed Firewall support

Terraform Provider VCD 3.5 introduced initial support for VDC Groups, but coverage for existing resources was still missing. We heard the demand loud and clear! This release focused on VDC Group support across our existing resources. This list of resources (including data sources) support VDC Groups now:

VDC Group support for these entities introduces a new field, owner_id which deprecates vdc field or by inheriting entity location from parent objects (e.g. vcd_network_routed_v2 inherits parent VDC or VDC Group from vcd_nsxt_edgegateway)

Distributed firewall

As our resources now support VDC Groups – Distributed Firewall management is now supported viavcd_nsxt_distributed_firewall and an additional data source for those that want to reference Network Context Profiles vcd_nsxt_network_context_profile.

More details in a new documentation page dedicated to VDC Group support in official documentation as well documentation for each affected resource is updated.

Metadata support in most resources

Seventeen resources with data sources received support for metadata.

It is easy to manage metadata:

resource "vcd_catalog" "myNewCatalog" {
  org = "my-org"

  name             = "my-catalog"
  description      = "catalog for files"
  delete_recursive = "true"
  delete_force     = "true"


  # 3.6.0 introduced fields
  metadata = {
    license = "public"
    version = "v1"
  }
}

resource "vcd_catalog" "myNewCatalog" {

org = "my-org"

name = "my-catalog"

description = "catalog for files"

delete_recursive = "true"

delete_force = "true"

# 3.6.0 introduced fields

metadata = {

license = "public"

version = "v1"

}

Ability to configure advanced compute settings for VM

The vcd_vapp_vm and vcd_vm gets the ability of configure advanced compute settings. Values are in MHz and MB.

resource "vcd_vapp" "web" {
  name = "web"
}

resource "vcd_vapp_vm" "advancedVM" {
  vapp_name     = vcd_vapp.web.name
  name          = "webApp"
  computer_name = "my webApp"
  memory        = 2048
  cpus          = 2
  cpu_cores     = 1

  os_type          = "sles10_64Guest"
  hardware_version = "vmx-14"
  catalog_name     = "my-catalog"
  boot_image       = "myMedia"

  # 3.6.0 introduced fields
  memory_priority    = "CUSTOM"
  memory_shares      = "480"
  memory_reservation = "8"
  memory_limit       = "48"

  cpu_priority    = "CUSTOM"
  cpu_shares      = "512"
  cpu_reservation = "200"
  cpu_limit       = "1000"
}

resource "vcd_vapp" "web" {

name = "web"

}

resource "vcd_vapp_vm" "advancedVM" {

vapp_name = vcd_vapp.web.name

name = "webApp"

computer_name = "my webApp"

memory = 2048

cpus = 2

cpu_cores = 1

os_type = "sles10_64Guest"

hardware_version = "vmx-14"

catalog_name = "my-catalog"

boot_image = "myMedia"

# 3.6.0 introduced fields

memory_priority = "CUSTOM"

memory_shares = "480"

memory_reservation = "8"

memory_limit = "48"

cpu_priority = "CUSTOM"

cpu_shares = "512"

cpu_reservation = "200"

cpu_limit = "1000"

}

Additional catalog and catalog item handling features

resource/vcd_catalog_item allows to upload OVF using URL using property ovf_url
resource/vcd_org allows configure catalog publish settings with properties can_publish_external_catalogs and can_subscribe_external_catalogs
resource/vcd_catalog allows to publish a catalog externally to make its vApp templates and media files available for subscription by organizations outside the Cloud Director installation

resource "vcd_org" "my-org" {
  name             = "my-org"
  full_name        = "My organization"
  description      = "The pride of my work"
  is_enabled       = "true"
  delete_recursive = "true"
  delete_force     = "true"

  # 3.6.0 introduced fields
  can_publish_external_catalogs   = true
  can_subscribe_external_catalogs = true
}


resource "vcd_catalog" "myNewCatalog" {
  org              = vcd_org.my-org.name
  name             = "my-catalog"
  description      = "catalog for files"
  delete_recursive = "true"
  delete_force     = "true"

  # 3.6.0 introduced fields
  publish_enabled               = true
  cache_enabled                 = true
  preserve_identity_information = true
  password                      = "my password"
}

resource "vcd_org" "my-org" {

name = "my-org"

full_name = "My organization"

description = "The pride of my work"

is_enabled = "true"

delete_recursive = "true"

delete_force = "true"

# 3.6.0 introduced fields

can_publish_external_catalogs = true

can_subscribe_external_catalogs = true

}

resource "vcd_catalog" "myNewCatalog" {

org = vcd_org.my-org.name

name = "my-catalog"

description = "catalog for files"

delete_recursive = "true"

delete_force = "true"

# 3.6.0 introduced fields

publish_enabled = true

cache_enabled = true

preserve_identity_information = true

password = "my password"

}

More information

Complete changelog with all improvements
Documentation in Hashicorp registry
A new guide page focused on VDC Group support

As always, as part of Terraform Provider VCD development, we improve underlying Go SDK for VMware Cloud Director and a new version v2.15 is released. Check changelog for more details.

Distributed firewall

Metadata support in most resources

Ability to configure advanced compute settings for VM

Additional catalog and catalog item handling features

More information

Related Articles

Terraform VMware Cloud Director Provider v3.13.0

Terraform VMware Cloud Director Provider v3.11.0

How to customize IP Spaces' IP allocation with Terraform