Terraform VMware Cloud Director (VCD) Provider v3.14.0 is offered 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 assets and seven new knowledge sources, 11 enhancements and 9 bugfixes.
API Filters and External Endpoints
API Filters permit to increase VCD API with customised URLs that may be redirected to an External Endpoint. These two ideas have now their respective assets within the Terraform supplier:
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 simple external endpoint example”
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 might be made to https://10.1.1.1/my-service with all of the request contents and question parameters coming from VCD.
ALB Virtual Service Policies
Three new assets and knowledge sources for managing ALB Virtual Service HTTP Policies. These assets can turn into fairly massive as a result of quantity of match standards and motion configuration, however one can discover examples in every of their very own documentation pages:
Improvements
Improved person expertise with RDE Behaviors
The assets and knowledge sources vcd_rde_interface_behavior and vcd_rde_type_behavior had the execution argument, which solely supported key-value mappings to outline conduct executions. This launch provides a brand new argument, execution_json, that enables to outline extra advanced conduct executions by offering a posh JSON string with the specification:
useful resource “vcd_rde_interface_behavior” “behavior” {
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 an everyday
# ‘execution’ map, like a nested “execution_properties” in a webhook conduct:
execution_json = jsonencode({
“type” : “WebHook”,
“id” : “testWebHook”,
“href” : “https://hooks.slack.com:443/services/T07UZFN0N/B01EW5NC42D/rfjhHCGIwzuzQFrpPZiuLkIX”,
“_internal_key” : “secretKey”,
“execution_properties” : {
“template” : {
“content” : “
},
“_secure_token” : “secureToken”,
“invocation_timeout” : 7
}
})
}
Note that the argument execution can nonetheless be used for less complicated definitions. Also, the vcd_rde_behavior_invocation knowledge supply permits to make use of JSON arguments as properly:
knowledge “vcd_rde_behavior_invocation” “invoke” {
rde_id = vcd_rde.rde.id
behavior_id = vcd_rde_interface_behavior.conduct.id
invoke_on_refresh = true
arguments_json = jsonencode({
“template” : {
“content” : “hello world”
},
“_secure_token” : “secureToken”,
“invocation_timeout” : 7
})
}
New knowledge supply for Catalog entry controls
With the brand new vcd_catalog_access_control knowledge 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).
Other notable enhancements
Bug fixes
Not all the things is listed right here, however there’s a checklist of person requested bug fixes that had been addressed and might be reviewed in changelog.
Go SDK v2.26.0 Released
Last however not least, there’s a new model v2.26.0 of Go SDK for VMware Cloud Director.