Releases: pivotal-cf/terraforming-azure
Releases · pivotal-cf/terraforming-azure
v0.13.0
- fix nsg configs to correctly flow traffic from Standard SKU load balancers.
- added dns subdomain variable.
v0.12.0
- Drops the suffix added to the env name to form the resource group name
- Switches load balancer to standard SKU
v0.11.0
- Adds aliases to make consistent names possible across terraforming-* repos
- Upgrades provider to resolve hashicorp/terraform-provider-azurerm#771
Known issues: diego ssh is not functional. We're researching the correct setup for forwarding cf ssh requests on Azure.
v0.10.0
Pin terraform provider to v1.0.0
due to current issue with public ip resource
v0.9.0
v0.8.0
0.7.0
0.6.0
0.5.0
New in this release
- Renames the
opsman_and_director_subnet
tomanagement_subnet
. This change is backwards-incompatible. All other subnet-related properties have also been renamed to align with this new naming scheme. - Adds storage account and container resources to support deploying ERT using external Azure storage for the blobstore.
- Changes subnet CIDR property outputs to lists so that they align with the other terraforming-IAAS repos.
- Removes the deprecated
location
property from many resources as they are no longer needed.
0.4.0
New in this release
- Adds an optional second Ops Manager VM. A common pattern for teams is to deploy two Ops Managers at the same time to facilitate testing an upgrade scenario. One Ops Manager with the old version, and a second one with the newer version.
- Deletes the Ops Manager OS disk when the VM is deleted. This fixes an issue that would prevent recreating the Ops Manager VM with a newer image.
- Simplifies the names of properties provided as outputs.
- Dynamically generates an SSH key-pair to be used to access the Ops Manager VM. The keys are available as outputs.