Release History

Version 0.8.0 - 2024-10-21

What's Changed

• version and output fixes by @jchancellor-ms in https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/pull/85
• chore: repository governance by @segraef in https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/pull/86

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/compare/v0.7.4...v0.8.0

Version 0.7.4 - 2024-09-12

What's Changed

• chore: repository governance by @segraef in https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/pull/74
• updated versions, ignore_changes on passwords by @jchancellor-ms in https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/pull/75

New Contributors

• @segraef made their first contribution in https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/pull/74

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/compare/v0.7.3...v0.7.4

Version 0.7.3 - 2024-08-16

What's Changed

• Public IP output addition by @jchancellor-ms in https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/pull/70

Full Changelog: https://github.com/Azure/terraform-azurerm-avm-res-avs-privatecloud/compare/v0.7.2...v0.7.3

Version 0.7.2 - 2024-07-15

This release updates the telemetry provider to use Terraform code.

Known Issues:

• There is currently a known issue when making expressRoute connections to VWAN ExpressRoute gateways that is a passthrough from an issue in the AzureRM provider. This issue has a fix PR that is pending review and merging. Upon a successful update from the AzureRM team, we will update this module to the require the latest minimum working version of the AzureRM provider.

Version 0.7.1 - 2024-06-12

This release is a bug fix to correct the minimum required provider versions to align with features used in the code. Users who had older provider versions were experiencing issues with new features introduced in the role assignments.

Version 0.7.0 - 2024-06-11

This release includes two major changes which can be breaking to existing implementations.

1. This release addresses connection issues reported in #50 which resulted in implementation failures when connecting to expressRoute gateways in another subscription and resource group. To correct this, the connection resources were moved from using the AzureRM provider to using the AzAPI provider so that full ID resource references could be used. This is then facilitated by including new inputs to reference another resource group and location when deploying the connection resource.
2. This release also addresses the need to be able to serialize expressRoute connections so that the install doesn't fail due to conflicting locks when simultaneously implementing the connections. Be aware that this works for the first two connections and 3 or more connections will result in a conflict requiring the apply to be re-run after the failure.

Minor changes in this release include:

• Updating sub-modules used in examples and testing to comply with the AVM spec
• Cleaning up documentation for inputs and outputs to make the module easier to use.

Input specific changes are:

• customer_managed_key input is now an object instead of a map of objects to comply with the AVM spec. Note: This input includes the default for user-assigned managed identities to be spec compliant, but this input is non-functional for AVS.
• expressroute_connections input replaces the use of the map key as the connection resource name and requires an explicit name input.
• expressroute_connections input includes a new deployment_order attribute which can be used to serialize the first two expressroute connections.
• expressroute_connections input includes the ability to deploy the connection to a separate resource group using the network_resource_group_resource_id and network_resource_group_location attributes.
• lock input updated to comply with the AVM spec schema.
• role_assignments input updated to comply with the AVM spec schema and defaults.
• tags input updated to comply with the AVM spec schema.

NOTE: There is a known bug with the AzureRM azurerm_express_route_connection resource used to make VWAN connections for AVS. Connections will fail with an 'unable to parse the request' message. We will hold an open issue on the repo until such time as the issue is resolved.

Version 0.6.1 - 2024-05-16

This release corrects a bug with the iScsi configuration in the recently added Elastic SAN interface.

NOTE: To properly use this module, it is required to include the following provider block and feature flag in your root module. If you are using other modules that use the AzAPI provider where this feature flag hasn't been implemented, then an alias with this flag will be required for this module. This requirement will go away when the AzAPI provider releases version v2.0 with this change as the default. We will update the module and notes accordingly when that occurs.

provider "azapi" {
  enable_hcl_output_for_data_source = true
}

Version 0.6.0 - 2024-05-15

This release introduces a new interface for configuring elastic SAN datastores. It includes examples demonstrating the use of the elasticSAN interface with a separate module example for creating and configuring an elasticSan configuration.

It also contains a fix for an issue reported where the run_command discovery would fail on rare occasions.

NOTE: To properly use this module, it is required to include the following provider block and feature flag in your root module. If you are using other modules that use the AzAPI provider where this feature flag hasn't been implemented, then an alias with this flag will be required for this module. This requirement will go away when the AzAPI provider releases version v2.0 with this change as the default. We will update the module and notes accordingly when that occurs.

provider "azapi" {
  enable_hcl_output_for_data_source = true
}

Version 0.5.0 - 2024-05-02

This release addresses breaking changes introduced by version v1.13.0 of the AzAPI provider. It modifies outputs, body, and other properties to use HCL objects instead of JSON going forward. It corrects a number of schema related failures that resulted from the improved schema checking in the AzAPI provider.

NOTE: To properly use this module, it is required to include the following provider block and feature flag in your root module. If you are using other modules that use the AzAPI provider where this feature flag hasn't been implemented, then an alias with this flag will be required for this module. This requirement will go away when the AzAPI provider releases version v2.0 with this change as the default. We will update the module and notes accordingly when that occurs.

provider "azapi" {
  enable_hcl_output_for_data_source = true
}

Version 0.4.1 - 2024-04-23

Bug Fix Release: This release corrects an issue where an error would occur during deployment if the extended_network_blocks for AV64 sku deployments was an empty list. This error is limited to new functionality released in v0.4.0.

Version 0.4.0 - 2024-04-16

Warning: This release contains a breaking change. The location input variable is now required.

This pull request includes the following:

• Corrects an issue where the use of data sources could result in unexpected deletions in rare edge cases
• Adds support for the AV64 sku by enabling the input of the ip segment(s) required for AV64
• Contains documentation fixes

Version 0.3.1 - 2024-02-21

Converted encryption to for_each from count to address apply issues.

Version 0.3.0 - 2024-02-21

Additional encryption fixes

Version 0.2.1 - 2024-02-21

CMK bug fixes

Version 0.2.0 - 2024-02-21

Correcting invalid null reference on the data source for customer managed keys.

Version 0.1.4 - 2024-02-20

Additional variable documentation changes for readability

Version 0.1.3 - 2024-02-20

More doc improvements for readability

Version 0.1.2 - 2024-02-20

Updating variable descriptions to improve registry documentation readability.

Version 0.1.1 - 2024-02-13

This is the first official release of the AVM Azure VMware Solution module. It implements most of the AVS API functionality with the supported interfaces.

 
 {
  "workingFolder": "packages",
  "packages": [
    // packages defined earlier
    {
      "name": "avm-terraform/avs-privatecloud",
      "version": "0.8.0"
    }
  ]
}

This package has no dependencies