Skip to content

Releases: pivotal-cf/terraforming-azure

v0.13.0

30 Jul 16:37
Compare
Choose a tag to compare
  • fix nsg configs to correctly flow traffic from Standard SKU load balancers.
  • added dns subdomain variable.

v0.12.0

14 May 20:30
Compare
Choose a tag to compare
  • Drops the suffix added to the env name to form the resource group name
  • Switches load balancer to standard SKU

v0.11.0

27 Mar 16:33
Compare
Choose a tag to compare

Known issues: diego ssh is not functional. We're researching the correct setup for forwarding cf ssh requests on Azure.

v0.10.0

30 Jan 00:41
Compare
Choose a tag to compare

Pin terraform provider to v1.0.0 due to current issue with public ip resource

v0.9.0

05 Jan 19:34
Compare
Choose a tag to compare
  • Add sensitive to outputs
  • Add security group for Ops Manager
  • Add option to automatically generate certs signed by a provided CA

v0.8.0

17 Nov 22:58
Compare
Choose a tag to compare
  • Updates for latest terraform
  • Rename ert resources to pas

0.7.0

06 Apr 21:53
Compare
Choose a tag to compare

New in this release:

  • Increase the number of storage account instances from 3 to 5 to allow a greater total number of disks (32 per instance)

0.6.0

27 Mar 23:48
Compare
Choose a tag to compare

New in this release:

  • Moves the isolation segment resources into a module. For more details about this change, see the README topic.

0.5.0

03 Mar 01:36
Compare
Choose a tag to compare

New in this release

  • Renames the opsman_and_director_subnet to management_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

14 Jan 01:00
Compare
Choose a tag to compare

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.