Skip to content

Latest commit

 

History

History
345 lines (255 loc) · 18.3 KB

CHANGELOG.md

File metadata and controls

345 lines (255 loc) · 18.3 KB
Raw

1.2.0 (Unreleased)

FEATURES:

  • New Resource: vsphere_custom_attribute [GH-229]
  • New Data Source: vsphere_custom_attribute [GH-229]

IMPROVEMENTS:

  • All vSphere provider that are capable of doing so now support custom attributes. Check the documentation of any specific resource for more details! [GH-229]
  • resource/vsphere_virtual_machine: The resource will now disallow a disk's name coming from a value that is still unavailable at plan time (such as a computed value from a resource). [GH-329]

1.1.1 (December 14, 2017)

IMPROVEMENTS:

  • resource/vsphere_virtual_machine: Network interface resource allocation options are now restricted to vSphere 6.0 and higher, as they are unsupported on vSphere 5.5. (#322)
  • resource/vsphere_virtual_machine: Resources that were deleted outside of Terraform will now be marked as gone in the state, causing them to be re-created during the next apply. (#321)
  • resource/vsphere_virtual_machine: Added some restrictions to storage vMotion to cover some currently un-supported scenarios that were still allowed, leading to potentially dangerous situations or invalid post-application states. (#319)
  • resource/vsphere_virtual_machine: The resource now treats disks that it does not recognize at a known device address as orphaned, and will set keep_on_remove to safely remove them. (#317)
  • resource/vsphere_virtual_machine: The resource now attempts to detect unsafe disk deletion scenarios that can happen from the renaming of a virtual machine in situations where the VM and disk names may share a common variable. The provider will block such operations from proceeding. (#305)

1.1.0 (December 07, 2017)

BREAKING CHANGES:

  • The vsphere_virtual_machine data source has a new sub-resource attribute for disk information, named disks. This takes the place of disk_sizes, which has been moved to a size attribute within this new sub-resource, and also contains information about the discovered disks' eagerly_scrub and thin_provisioned settings. This is to facilitate the ability to discover all settings that could cause issues when cloning virtual machines.

To transition to the new syntax, any disk sub-resource in a vsphere_virtual_machine resource that depends on a syntax such as:

resource "vsphere_virtual_machine" "vm" {
  ...

  disk {
    name = "terraform-test.vmdk"
    size = "${data.vsphere_virtual_machine.template.disk_sizes[0]}"
  }
}

Should be changed to:

resource "vsphere_virtual_machine" "vm" {
  ...

  disk {
    name = "terraform-test.vmdk"
    size = "${data.vsphere_virtual_machine.template.disks.0.size}"
  }
}

If you are using linked_clone, add the new settings for eagerly_scrub and thin_provisioned:

resource "vsphere_virtual_machine" "vm" {
  ...

  disk {
    name             = "terraform-test.vmdk"
    size             = "${data.vsphere_virtual_machine.template.disks.0.size}"
    eagerly_scrub    = "${data.vsphere_virtual_machine.template.disks.0.eagerly_scrub}"
    thin_provisioned = "${data.vsphere_virtual_machine.template.disks.0.thin_provisioned}"
  }
}

For a more complete example, see the cloning and customization example in the documentation.

BUG FIXES:

  • resource/vsphere_virtual_machine: Fixed a bug with NIC device assignment logic that was causing a crash when adding more than 3 NICs to a VM. (#280)
  • resource/vsphere_virtual_machine: CDROM devices on cloned virtual machines are now connected properly on power on. (#278)
  • resource/vsphere_virtual_machine: Tightened the pre-clone checks for virtual disks to ensure that the size and disk types are the same between the template and the created virtual machine's configuration. (#277)

1.0.3 (December 06, 2017)

BUG FIXES:

  • resource/vsphere_virtual_machine: Fixed an issue in the post-clone process when a CDROM device exists in configuration. (#276)

1.0.2 (December 05, 2017)

BUG FIXES:

  • resource/vsphere_virtual_machine: Fixed issues related to correct processing VM templates with no network interfaces, or fewer network interfaces than the amount that will ultimately end up in configuration. (#269)
  • resource/vsphere_virtual_machine: Version comparison logic now functions correctly to properly disable certain features when using older versions of vSphere. (#272)

1.0.1 (December 02, 2017)

BUG FIXES:

  • resource/vsphere_virtual_machine: Corrected an issue that was preventing the use of this resource on standalone ESXi. (#263)
  • data/vsphere_resource_pool: This data source now works as documented on standalone ESXi. (#263)

1.0.0 (December 01, 2017)

BREAKING CHANGES:

  • The vsphere_virtual_machine resource has received a major update and change to its interface. See the documentation for the resource for full details, including information on things to consider while migrating the new version of the resource.

FEATURES:

  • New Data Source: vsphere_resource_pool (#244)
  • New Data Source: vsphere_datastore (#244)
  • New Data Source: vsphere_virtual_machine (#244)

IMPROVEMENTS:

  • resource/vsphere_virtual_machine: The distinct VM workflows are now better defined: all cloning options are now contained within a clone sub-resource, with customization being a customize sub-resource off of that. Absence of the clone sub-resource means no cloning or customization will occur. (#244)
  • resource/vsphere_virtual_machine: Nearly all customization options have now been exposed. Magic values such as hostname and DNS defaults have been removed, with some of these options now being required values depending on the OS being customized. (#244)
  • resource/vsphere_virtual_machine: Device management workflows have been greatly improved, exposing more options and fixing several bugs. (#244)
  • resource/vsphere_virtual_machine: Added support for CPU and memory hot-plug. Several other VM reconfiguration operations are also supported while the VM is powered on, guest type and VMware tools permitting in some cases. (#244)
  • resource/vsphere_virtual_machine: The resource now supports both host and storage vMotion. Virtual machines can now be moved between hosts, clusters, resource pools, and datastores. Individual disks can be pinned to a single datastore with a VM located in another. (#244)
  • resource/vsphere_virtual_machine: The resource now supports import. (#244)
  • resource/vsphere_virtual_machine: Several other minor improvements, see documentation for more details. (#244)

BUG FIXES:

  • resource/vsphere_virtual_machine: Several long-standing issues have been fixed, namely surrounding virtual disk and network device management. (#244)
  • resource/vsphere_host_virtual_switch: This resource now correctly supports a configuration with no NICs. (#256)
  • data/vsphere_network: No longer restricted to being used on vCenter. (#248)

0.4.2 (October 13, 2017)

FEATURES:

  • New Data Source: vsphere_network (#201)
  • New Data Source: vsphere_distributed_virtual_switch (#170)
  • New Resource: vsphere_distributed_port_group (#189)
  • New Resource: vsphere_distributed_virtual_switch (#188)

IMPROVEMENTS:

  • resource/vsphere_virtual_machine: The customization waiter is now tunable through the wait_for_customization_timeout argument. The timeout can be adjusted or the waiter can be disabled altogether. (#199)
  • resource/vsphere_virtual_machine: domain now acts as a default for dns_suffixes if the latter is not defined, setting the value in domain as a search domain in the customization specification. vsphere.local is not used as a last resort only. (#185)
  • resource/vsphere_virtual_machine: Expose the adapter_type parameter to allow the control of the network interface type. This is currently restricted to vmxnet3 and e1000 but offers more control than what was available before, and more interface types will follow in later versions of the provider. (#193)

BUG FIXES:

  • resource/vsphere_virtual_machine: Fixed a regression with network discovery that was causing Terraform to crash while the VM was in a powered off state. (#198)
  • All resources that can use tags will now properly remove their tags completely (or remove any out-of-band added tags) when the tags argument is not present in configuration. (#196)

0.4.1 (October 02, 2017)

BUG FIXES:

  • resource/vsphere_folder: Migration of state from a version of this resource before v0.4.0 now works correctly. (#187)

0.4.0 (September 29, 2017)

BREAKING CHANGES:

  • The vsphere_folder resource has been re-written, and its configuration is significantly different. See the resource documentation for more details. Existing state will be migrated. (#179)

FEATURES:

  • New Data Source: vsphere_tag (#171)
  • New Data Source: vsphere_tag_category (#167)
  • New Resoruce: vsphere_tag (#171)
  • New Resoruce: vsphere_tag_category (#164)

IMPROVEMENTS:

  • resource/vsphere_folder: You can now create any kind of folder with this resource, not just virtual machine folders. (#179)
  • resource/vsphere_folder: Now supports tags. (#179)
  • resource/vsphere_folder: Now supports import. (#179)
  • resource/vsphere_datacenter: Tags can now be applied to datacenters. (#177)
  • resource/vsphere_nas_datastore: Tags can now be applied to NAS datastores. (#176)
  • resource/vsphere_vmfs_datastore: Tags can now be applied to VMFS datastores. (#176)
  • resource/vsphere_virtual_machine: Tags can now be applied to virtual machines. (#175)
  • resource/vsphere_virtual_machine: Adjusted the customization timeout to 10 minutes (#168)

BUG FIXES:

  • resource/vsphere_virtual_machine: This resource can now be used with networks with unescaped slashes in its network name. (#181)
  • resource/vsphere_virtual_machine: Fixed a crash where virtual NICs were created with networks backed by a 3rd party hardware VDS. (#181)
  • resource/vsphere_virtual_machine: Fixed crashes and spurious diffs that were caused by errors in the code that associates the default gateway with its correct network device during refresh. (#180)

0.3.0 (September 14, 2017)

BREAKING CHANGES:

  • vsphere_virtual_machine now waits on a routeable IP address by default, and does not wait when running terraform plan, terraform refresh, or terraform destroy. There is also now a timeout of 5 minutes, after which terraform apply will fail with an error. Note that the apply may not fail exactly on the 5 minute mark. The network waiter can be disabled completely by setting wait_for_guest_net to false. (#158)

FEATURES:

  • New Resource: vsphere_virtual_machine_snapshot (#107)

IMPROVEMENTS:

  • resource/vsphere_virtual_machine: Virtual machine power state is now enforced. Terraform will trigger a diff if the VM is powered off or suspended, and power it back on during the next apply. (#152)

BUG FIXES:

  • resource/vsphere_virtual_machine: Fixed customization behavior to watch customization events for success, rather than returning immediately when the CustomizeVM task returns. This is especially important during Windows customization where a large part of the customization task involves out-of-band configuration through Sysprep. (#158)

0.2.2 (September 07, 2017)

FEATURES:

  • New Resource: vsphere_nas_datastore (#149)
  • New Resource: vsphere_vmfs_datastore (#142)
  • New Data Source: vsphere_vmfs_disks (#141)

0.2.1 (August 31, 2017)

FEATURES:

  • New Resource: vsphere_host_port_group (#139)
  • New Resource: vsphere_host_virtual_switch (#138)
  • New Data Source: vsphere_datacenter (#144)
  • New Data Source: vsphere_host (#146)

IMPROVEMENTS:

  • resource/vsphere_virtual_machine: Allow customization of hostname (#79)

BUG FIXES:

  • resource/vsphere_virtual_machine: Fix IPv4 address mapping issues causing spurious diffs, in addition to IPv6 normalization issues that can lead to spurious diffs as well. (#128)

0.2.0 (August 23, 2017)

BREAKING CHANGES:

  • resource/vsphere_virtual_disk: Default adapter type is now lsiLogic, changed from ide. (#94)

FEATURES:

  • New Resource: vsphere_datacenter (#126)
  • New Resource: vsphere_license (#110)

IMPROVEMENTS:

  • resource/vsphere_virtual_machine: Add annotation argument (#111)

BUG FIXES:

  • Updated govmomi to v0.15.0 (#114)
  • Updated network interface discovery behaviour in refresh. [#129]. This fixes several reported bugs - see the PR for references!

0.1.0 (June 20, 2017)

NOTES:

  • Same functionality as that of Terraform 0.9.8. Repacked as part of Provider Splitout