Terraform VMware Cloud Director Supplier v3.14.0

Terraform VMware Cloud Director (VCD) Supplier v3.14.0 is out there now, and it helps VCD variations from 10.4.0 to 10.6.0. This launch delivers options and enhancements actively requested by the customers. It accommodates 5 new sources and seven new information sources, 11 enhancements and 9 bugfixes.

Table of Contents

API Filters and Exterior Endpoints

API Filters enable to increase VCD API with customised URLs that may be redirected to an Exterior Endpoint. These two ideas have now their respective sources within the Terraform supplier:

Right here’s an instance that exhibits the way to use them:

useful resource “vcd_external_endpoint” “ep1”
vendor = “broadcom”
title = “my-endpoint”
model = “1.0.0”
enabled = true
description = “A easy exterior endpoint instance”
root_url = “https://10.1.1.1/my-service”

useful resource “vcd_api_filter” “af”
external_endpoint_id = vcd_external_endpoint.ep1.id
url_matcher_pattern = “/my-service/.*”
url_matcher_scope = “EXT_API”

When this configuration is utilized, all requests which can be made to <vcd-url>/ext-api/my-service/... might be redirected to https://10.1.1.1/my-service with all of the request contents and question parameters coming from VCD.

ALB Digital Service Insurance policies

Three new sources and information sources for managing ALB Digital Service HTTP Insurance policies. These sources can change into fairly massive because of the quantity of match standards and motion configuration, however one can discover examples in every of their very own documentation pages:

Enhancements

Improved person expertise with RDE Behaviors

The sources and information sources vcd_rde_interface_behavior and vcd_rde_type_behavior had the execution argument, which solely supported key-value mappings to outline habits executions. This launch provides a brand new argument, execution_json, that permits to outline extra advanced habits executions by offering a fancy JSON string with the specification:

useful resource “vcd_rde_interface_behavior” “habits”
rde_interface_id = vcd_rde_interface.my_interface.id
title = “MyBehavior”

# ‘execution_json’ permits to make use of advanced constructions that aren’t doable with a daily
# ‘execution’ map, like a nested “execution_properties” in a webhook habits:
execution_json = jsonencode(
“kind” : “WebHook”,
“id” : “testWebHook”,
“href” : “https://hooks.slack.com:443/companies/T07UZFN0N/B01EW5NC42D/rfjhHCGIwzuzQFrpPZiuLkIX”,
“_internal_key” : “secretKey”,
“execution_properties” :
“template” :
“content material” : “<template_content_string>”
,
“_secure_token” : “secureToken”,
“invocation_timeout” : 7

)

Word that the argument execution can nonetheless be used for easier definitions. Additionally, the vcd_rde_behavior_invocation information supply permits to make use of JSON arguments as nicely:

information “vcd_rde_behavior_invocation” “invoke”
rde_id = vcd_rde.rde.id
behavior_id = vcd_rde_interface_behavior.habits.id
invoke_on_refresh = true
arguments_json = jsonencode(
“template” :
“content material” : “whats up world”
,
“_secure_token” : “secureToken”,
“invocation_timeout” : 7
)

New information supply for Catalog entry controls

With the brand new vcd_catalog_access_control information supply, one can learn Catalog entry controls, and all the data it offers in its attributes (just like the Organisations which the Catalog is shared with).

Different notable enhancements

Bug fixes

Not all the pieces is listed right here, however there’s a checklist of person requested bug fixes that had been addressed and might be reviewed in changelog.