The launch time for model 3.9.0 of Terraform VMware Cloud Director Provider is approaching,
and for the primary time, we’re releasing a beta, so customers can strive the brand new options and provides useful suggestions that may enhance the ultimate launch.
What is a “beta” construct?
A beta construct is a preliminary launch of an meant new versioned software program, which accommodates all (or most) of the scheduled options, however has not been exhaustively examined but.
This type of launch goals to provide customers an opportunity to strive new options and provides early suggestions, making the ultimate launch extra sturdy.
Thus, we encourage customers to strive the beta construct and report errors within the code habits or documentation by opening a problem and indicating that the report is concerning the beta model.
How to make use of a beta launch
The beta launch is offered to customers in the identical place the place the common releases are, in order that customers can get it by utilizing terraform init
, like all common launch. The foremost distinction is that to make use of a beta launch, it is advisable to specify the precise model of the supplier, like this one:
terraform { required_providers { vcd = { supply = “vmware/vcd” model = “3.9.0-beta.2” } } required_version = “>= 1.3.0” } |
Inexact operators like “~>” or “>=” won’t match the beta releases.
Main options of this beta construct
- External community and Tier 0 (supplier) gateway administration useful resource
vcd_external_network_v2
permits setting DNS fieldsdns1
,dns2
anddns_suffix
for NSX-T backed entities in order that it may be inherited by direct Org VDC networks - NSX-T Load Balancer configuration useful resource and knowledge supply
vcd_nsxt_alb_settings
now help IPv6 and clear mode configuration utilizing two new fieldsis_transparent_mode_enabled
andipv6_service_network_specification
- Introducing help of the Runtime Defined Entity (RDE) framework, that enables prospects to increase the present capabilities of VCD, with the addition of the next sources and knowledge sources:
vcd_rde_interface
useful resource to permit customers to create and handle RDE Interfaces, which can be utilized to outline RDE Types.vcd_rde_type
useful resource to create and handle RDE Types, which can be utilized
to create Runtime Defined Entities.vcd_rde
useful resource to create and handle Runtime Defined Entities, which can be utilized to increase VCD with new customised options.- Data sources to fetch current RDE Interfaces (
vcd_rde_interface
), RDE Types (vcd_rde_type
) and Runtime Defined Entities (vcd_rde
).
- New useful resource
vcd_nsxv_distributed_firewall
to set and keep visitors guidelines for the entry to a NSX-V VDC entities. Ancillary knowledge sourcesvcd_nsxv_application_finder
,vcd_nsxv_application
, andvcd_nsxv_application_group
facilitate entry and
utilization to pre-defined functions and utility teams utilized in firewall guidelines. - NSX-T Edge Gateway useful resource
vcd_nsxt_edgegateway
has two new configuration modes for automated IP allocation administration by utilizingsubnet_with_ip_count
,subnet_with_total_ip_count
andtotal_allocated_ip_count
fields
Main enhancements
- vApp community administration sources
vcd_vapp_network
andvcd_vapp_org_network
add
comfort flagreboot_vapp_on_removal
. It improves workflows with VCD variations 10.4.1 and above which return an error when eradicating vApp networks from powered on vApps. - The error message generated when making an attempt to authenticate a supplier with an invalid password
has been enhanced to enhance accuracy. - Organization group administration useful resource
vcd_org_group
provides help forOAUTH
id supplier sort. - The
vcd_vapp_network
useful resource now features aprefix_length
discipline, permitting the creation of IPv6 networks.