Skip to content

Commit

Permalink
Update CHANGELOG.md with v3.10.0 changes (#1088)
Browse files Browse the repository at this point in the history
* Update CHANGELOG.md with v3.10.0 changes
* Update go-vcloud-director dependency

---------

Signed-off-by: Giuseppe Maxia <[email protected]>
  • Loading branch information
dataclouder authored Jul 20, 2023
1 parent d47d46e commit 2df7e58
Show file tree
Hide file tree
Showing 6 changed files with 106 additions and 7 deletions.
1 change: 1 addition & 0 deletions .changes/v3.10.0/1030-features.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* Add a **new guide** to create and manage Kubernetes Clusters using Container Service Extension v4.0 [GH-1030]
2 changes: 1 addition & 1 deletion .changes/v3.10.0/1076-features.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
* **New Resource:** `vcd_nsxt_distributed_firewall_rule` to manage NSX-T Distributed Firewall one by
one. Rules will *not be created in parallel* because the API provides no direct endpoint to create
a single rule and this functionality uses a custom made function that abstracts the "update all"
a single rule and this functionality uses a custom-made function that abstracts the "update all"
endpoint. [GH-1076]
* **New Data Source:** `vcd_nsxt_distributed_firewall_rule` to read NSX-T Distributed Firewall one
by one [GH-1076]
100 changes: 98 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,102 @@
## 3.10.0 (TBC)
## 3.10.0 (July 20, 2023)

Changes in progress for v3.10.0 are available at [.changes/v3.10.0](https://github.com/vmware/terraform-provider-vcd/tree/main/.changes/v3.10.0) until the release.
### FEATURES
* Add a **new guide** to create and manage Kubernetes Clusters using Container Service Extension v4.0 ([#1030](https://github.com/vmware/terraform-provider-vcd/pull/1030))
* **New Resource:** `vcd_nsxt_edgegateway_dhcp_forwarding` to manage NSX-T Edge Gateway DHCP Forwarding configuration ([#1056](https://github.com/vmware/terraform-provider-vcd/pull/1056))
* **New Data Source:** `vcd_nsxt_edgegateway_dhcp_forwarding` to read NSX-T Edge Gateway DHCP Forwarding configuration ([#1056](https://github.com/vmware/terraform-provider-vcd/pull/1056))
* **New Resource:** `vcd_ui_plugin` to programmatically install and manage UI Plugins ([#1059](https://github.com/vmware/terraform-provider-vcd/pull/1059))
* **New Data Source:** `vcd_ui_plugin` to fetch existing UI Plugins ([#1059](https://github.com/vmware/terraform-provider-vcd/pull/1059))
* **New Resource:** `vcd_ip_space` to manage IP Spaces in VCD 10.4.1+ ([#1061](https://github.com/vmware/terraform-provider-vcd/pull/1061))
* **New Data Source:** `vcd_ip_space` to read IP Spaces in VCD 10.4.1+ ([#1061](https://github.com/vmware/terraform-provider-vcd/pull/1061))
* **New Resource:** `vcd_ip_space_uplink` to manage IP Space Uplinks for External Networks (Provider
gateways) in VCD 10.4.1+ ([#1062](https://github.com/vmware/terraform-provider-vcd/pull/1062))
* **New Data Source:** `vcd_ip_space_uplink` to read IP Space Uplinks for External Networks
(Provider gateways) in VCD 10.4.1+ ([#1062](https://github.com/vmware/terraform-provider-vcd/pull/1062))
* **New Resource:** `vcd_ip_space_ip_allocation` to manage IP Space IP Allocations in VCD 10.4.1+
([#1062](https://github.com/vmware/terraform-provider-vcd/pull/1062))
* **New Data Source:** `vcd_ip_space_ip_allocation` to read IP Space IP Allocations in VCD 10.4.1+
([#1062](https://github.com/vmware/terraform-provider-vcd/pull/1062))
* **New Resource:** `vcd_ip_space_custom_quota` to manage Custom IP Space Quotas for individual
Organizations in VCD 10.4.1+ ([#1062](https://github.com/vmware/terraform-provider-vcd/pull/1062))
* **New Data Source:** `vcd_ip_space_custom_quota` to read Custom IP Space Quotas for individual
Organizations in VCD 10.4.1+ ([#1062](https://github.com/vmware/terraform-provider-vcd/pull/1062))
* **New Resource:** `vcd_org_saml` to manage an organization SAML configuration ([#1064](https://github.com/vmware/terraform-provider-vcd/pull/1064))
* **New Data Source:** `vcd_org_saml` to read an organization SAML configuration ([#1064](https://github.com/vmware/terraform-provider-vcd/pull/1064))
* **New Data Source:** `vcd_org_saml_metadata` to read an organization SAML service provider metadata ([#1064](https://github.com/vmware/terraform-provider-vcd/pull/1064))
* **New Resource:** `vcd_api_token` to manage API tokens ([#1070](https://github.com/vmware/terraform-provider-vcd/pull/1070))
* **New Resource:** `vcd_service_account` to manage Service Accounts ([#1070](https://github.com/vmware/terraform-provider-vcd/pull/1070))
* **New Data Source:** `vcd_service_account` to read Service Accounts ([#1070](https://github.com/vmware/terraform-provider-vcd/pull/1070))
* **New Resource:** `vcd_nsxt_edgegateway_dhcpv6` to manage NSX-T Edge Gateway DHCPv6 configuration
([#1071](https://github.com/vmware/terraform-provider-vcd/pull/1071),[#1083](https://github.com/vmware/terraform-provider-vcd/pull/1083))
* **New Data Source:** `vcd_nsxt_edgegateway_dhcpv6` to read NSX-T Edge Gateway DHCPv6 configuration
([#1071](https://github.com/vmware/terraform-provider-vcd/pull/1071),[#1083](https://github.com/vmware/terraform-provider-vcd/pull/1083))
* **New Resource:** `vcd_provider_vdc` to manage provider VDCs ([#1073](https://github.com/vmware/terraform-provider-vcd/pull/1073))
* **New Data Source:** `vcd_resource_pool` to read vCenter Resource Pools ([#1073](https://github.com/vmware/terraform-provider-vcd/pull/1073))
* **New Data Source:** `vcd_network_pool` to read Network Pools ([#1073](https://github.com/vmware/terraform-provider-vcd/pull/1073))
* **New Resource:** `vcd_rde_interface_behavior` to manage RDE Interface Behaviors, which can be invoked by RDEs and
overridden by RDE Types ([#1074](https://github.com/vmware/terraform-provider-vcd/pull/1074))
* **New Data Source:** `vcd_rde_interface_behavior` to read RDE Interface Behaviors, so they can be used
in RDE Type Behavior overrides ([#1074](https://github.com/vmware/terraform-provider-vcd/pull/1074))
* **New Resource:** `vcd_rde_type_behavior` to manage Behaviors in RDE Types, which can override those defined
in RDE Interfaces ([#1074](https://github.com/vmware/terraform-provider-vcd/pull/1074))
* **New Data Source:** `vcd_rde_type_behavior` to read RDE Type Behaviors ([#1074](https://github.com/vmware/terraform-provider-vcd/pull/1074))
* **New Resource:** `vcd_rde_type_behavior_acl` to manage the access to Behaviors in RDE Types and RDE Interfaces ([#1074](https://github.com/vmware/terraform-provider-vcd/pull/1074))
* **New Data Source:** `vcd_rde_type_behavior_acl` to read Access Levels from Behaviors of RDE Types and RDE Interfaces ([#1074](https://github.com/vmware/terraform-provider-vcd/pull/1074))
* **New Resource:** `vcd_nsxt_edgegateway_static_route` to manage NSX-T Edge Gateway Static Routes
on VCD 10.4.0+ ([#1075](https://github.com/vmware/terraform-provider-vcd/pull/1075))
* **New Data Source:** `vcd_nsxt_edgegateway_static_route` to read NSX-T Edge Gateway Static Routes
on VCD 10.4.0+ ([#1075](https://github.com/vmware/terraform-provider-vcd/pull/1075))
* **New Resource:** `vcd_nsxt_distributed_firewall_rule` to manage NSX-T Distributed Firewall one by
one. Rules will *not be created in parallel* because the API provides no direct endpoint to create
a single rule and this functionality uses a custom-made function that abstracts the "update all"
endpoint ([#1076](https://github.com/vmware/terraform-provider-vcd/pull/1076))
* **New Data Source:** `vcd_nsxt_distributed_firewall_rule` to read NSX-T Distributed Firewall one
by one ([#1076](https://github.com/vmware/terraform-provider-vcd/pull/1076))
* **New Resource:** `vcd_cloned_vapp` to create a vApp from either a vApp template or another vApp ([#1081](https://github.com/vmware/terraform-provider-vcd/pull/1081))

### EXPERIMENTAL
(_Experimental features and improvements may change in future releases, until declared stable._)
* Add `ignore_metadata_changes` argument to the Provider configuration to be able to specify metadata entries that should **not**
be managed by Terraform when using `metadata_entry` configuration blocks ([#1057](https://github.com/vmware/terraform-provider-vcd/pull/1057), [#1089](https://github.com/vmware/terraform-provider-vcd/pull/1089))

### IMPROVEMENTS
* The guide to install the Container Service Extension v4.0 now additionally explains how to install the
Kubernetes Container Clusters UI Plugin ([#1059](https://github.com/vmware/terraform-provider-vcd/pull/1059))
* `vcd_external_network_v2` resource and data source support IP Spaces on VCD 10.4.1+ by adding
`use_ip_spaces` and `dedicated_org_id` fields ([#1062](https://github.com/vmware/terraform-provider-vcd/pull/1062))
* `vcd_nsxt_edgegateway` resource supports IP Spaces by not requiring `subnet` specification
([#1062](https://github.com/vmware/terraform-provider-vcd/pull/1062))
* Resource and data source `vcd_nsxt_alb_virtual_service` support IPv6 on VCD 10.4.0+ via new field
`ipv6_virtual_ip_address` ([#1071](https://github.com/vmware/terraform-provider-vcd/pull/1071))
* Resource and data source `vcd_network_routed_v2` support Dual-Stack mode using
`dual_stack_enabled` and `secondary_gateway`, `secondary_prefix_length`,
`secondary_static_ip_pool` fields ([#1071](https://github.com/vmware/terraform-provider-vcd/pull/1071))
* Resource and data source `vcd_network_isolated_v2` support Dual-Stack mode using
`dual_stack_enabled` and `secondary_gateway`, `secondary_prefix_length`,
`secondary_static_ip_pool` fields ([#1071](https://github.com/vmware/terraform-provider-vcd/pull/1071))
* Resource and data source `vcd_nsxt_network_imported` support Dual-Stack mode using
`dual_stack_enabled` and `secondary_gateway`, `secondary_prefix_length`,
`secondary_static_ip_pool` fields ([#1071](https://github.com/vmware/terraform-provider-vcd/pull/1071))
* Resource and data source `vcd_nsxt_network_dhcp_binding` support `dhcp_v6_config` config ([#1071](https://github.com/vmware/terraform-provider-vcd/pull/1071))
* Validate possibility to perform end to end IPv6 configuration via additional tests ([#1071](https://github.com/vmware/terraform-provider-vcd/pull/1071))
* Resource `vcd_vdc_group` adds new field `remove_default_firewall_rule` to remove default
Distributed Firewall Rule after creation ([#1076](https://github.com/vmware/terraform-provider-vcd/pull/1076))
* The attribute `description` of `vcd_vm_placement_policy` is now Computed, as latest VCD versions set a default description
automatically if it is not set ([#1082](https://github.com/vmware/terraform-provider-vcd/pull/1082))

### BUG FIXES
* Fix [Issue #1058](https://github.com/vmware/terraform-provider-vcd/issues/1058) - Multiple `SYSTEM` scope data source `vcd_nsxt_app_port_profile` when multiple NSX-T managers are configured ([#1065](https://github.com/vmware/terraform-provider-vcd/pull/1065))
* Fix [Issue #1069](https://github.com/vmware/terraform-provider-vcd/issues/1069) - Inconsistent `security_profile_customization` field during `vcd_nsxt_ipsec_vpn_tunnel` update ([#1072](https://github.com/vmware/terraform-provider-vcd/pull/1072))
* Fix [Issue #1066](https://github.com/vmware/terraform-provider-vcd/issues/1066) - Not possible to handle more than 128 storage profiles ([#1073](https://github.com/vmware/terraform-provider-vcd/pull/1073))
* Fix a bug that caused `vcd_catalog` creation to fail if it is created with deprecated `metadata` argument in VCD 10.5 ([#1085](https://github.com/vmware/terraform-provider-vcd/pull/1085))

### NOTES
* Internal - replaces `takeBoolPointer`, `takeIntPointer`, `takeInt64Pointer` with generic `addrOf`
([#1055](https://github.com/vmware/terraform-provider-vcd/pull/1055))
* Bump `terraform-plugin-sdk` to v2.27.0 ([#1079](https://github.com/vmware/terraform-provider-vcd/pull/1079))
* Resource `vcd_nsxt_edgegateway_bgp_configuration` will send existing `GracefulRestart` to avoid
API validation errors in VCD 10.5.0+ ([#1083](https://github.com/vmware/terraform-provider-vcd/pull/1083))
* [`go-vcloud-director`](https://github.com/vmware/go-vcloud-director), the SDK this provider uses for low level access to the VCD, released with version v2.21.0

## 3.9.0 (April 27, 2023)

Expand Down
2 changes: 1 addition & 1 deletion go.mod
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ require (
github.com/hashicorp/go-version v1.6.0
github.com/hashicorp/terraform-plugin-sdk/v2 v2.27.0
github.com/kr/pretty v0.2.1
github.com/vmware/go-vcloud-director/v2 v2.21.0-alpha.13
github.com/vmware/go-vcloud-director/v2 v2.21.0
)

require (
Expand Down
4 changes: 2 additions & 2 deletions go.sum
Original file line number Diff line number Diff line change
Expand Up @@ -123,8 +123,8 @@ github.com/vmihailenco/msgpack/v5 v5.3.5 h1:5gO0H1iULLWGhs2H5tbAHIZTV8/cYafcFOr9
github.com/vmihailenco/msgpack/v5 v5.3.5/go.mod h1:7xyJ9e+0+9SaZT0Wt1RGleJXzli6Q/V5KbhBonMG9jc=
github.com/vmihailenco/tagparser/v2 v2.0.0 h1:y09buUbR+b5aycVFQs/g70pqKVZNBmxwAhO7/IwNM9g=
github.com/vmihailenco/tagparser/v2 v2.0.0/go.mod h1:Wri+At7QHww0WTrCBeu4J6bNtoV6mEfg5OIWRZA9qds=
github.com/vmware/go-vcloud-director/v2 v2.21.0-alpha.13 h1:eqX9yaNIXy7CQMD2A/Do/pNyM+Sbza9TEKAwOWcah10=
github.com/vmware/go-vcloud-director/v2 v2.21.0-alpha.13/go.mod h1:QPxGFgrUcSyzy9IlpwDE4UNT3tsOy2047tJOPEJ4nlw=
github.com/vmware/go-vcloud-director/v2 v2.21.0 h1:zIONrJpM+Fj+rDyXmsRfMAn1sP5WAP87USL0T9GS4DY=
github.com/vmware/go-vcloud-director/v2 v2.21.0/go.mod h1:QPxGFgrUcSyzy9IlpwDE4UNT3tsOy2047tJOPEJ4nlw=
github.com/xanzy/ssh-agent v0.3.3 h1:+/15pJfg/RsTxqYcX6fHqOXZwwMP+2VyYWJeWM2qQFM=
github.com/zclconf/go-cty v1.13.2 h1:4GvrUxe/QUDYuJKAav4EYqdM47/kZa672LwmXFmEKT0=
github.com/zclconf/go-cty v1.13.2/go.mod h1:YKQzy/7pZ7iq2jNFzy5go57xdxdWoLLpaEp4u238AE0=
Expand Down
4 changes: 3 additions & 1 deletion website/docs/index.html.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -410,12 +410,14 @@ The following arguments are used to configure the VMware Cloud Director Provider
* `import_separator` - (Optional; *v2.5+*) The string to be used as separator with `terraform import`. By default
it is a dot (`.`).

* `ignore_metadata_changes` - (Optional; *v3.10+*) Use one or more of these blocks to ignore specific metadata entries from being changed by this Terraform provider
* `ignore_metadata_changes` - (Optional; Experimental; *v3.10+*) Use one or more of these blocks to ignore specific metadata entries from being changed by this Terraform provider
after creation or when they were created outside Terraform.
See ["Ignore Metadata Changes"](#ignore-metadata-changes) for more details.

## Ignore metadata changes

=> This is an **EXPERIMENTAL FEATURE** that may change in a future release.

One or more `ignore_metadata_changes` blocks can be optionally set in the provider configuration, which will allow to ignore specific `metadata_entry`
items during all Terraform operations. This is useful, for example, to avoid removing metadata entries that were created
by an external actor, or after they were created by Terraform.
Expand Down

0 comments on commit 2df7e58

Please sign in to comment.