8 Commits (d-powershell-generated-docs)

Author	SHA1	Message	Date
Matthew Hooker	e41e99954d	go 1.11 format rules	8 years ago
Paul Meyer	09ce3c9803	Make it compile again	8 years ago
Matthew Hooker	ebe995c0ff	run goimports	8 years ago
Christopher Boumenot	0d427939bc	azure: Fix custom managed images ... I missed a change in my SDK update, and when I integrated this missing change I broke custom images.	9 years ago
Christopher Boumenot	d782ad99f8	azure: pick better names ... Use custom_managed_image_name to represent managed images use to build Packer VMs. Use managed_image_name to represent the image produced by Packer.	9 years ago
Christopher Boumenot	c6ff4aae59	Support for building from custom managed images	9 years ago
Christopher Boumenot	e42b3d8447	azure: fix error message ... There have been two issues raised where the user followed the error message, but they needed to add yet another config value to disambiguate the VNET. It would be better if the message over corrected, and asked the user to specify everything to ensure complete disambiguation.	10 years ago
Christopher Boumenot	871ca8c3d9	azure: Support for a user define VNET. ... Two new configuration options have been exposed to allow users to specify an existing virtual network: virtual_network_name and virtual_network_resource_group_name. * virtual_network_name: name of the virtual network to attach a Packer VM to. * virtual_network_resource_group_name: name of the resource group that contains the virtual network. This value is optional. If the value is not specified, the builder queries Azure for the appropriate value. If the builder cannot disambiguate the value, a value must be provided for this setting. * virtual_network_subnet_name: name of the subnet attached to the virtual network. This value is optional. If the value is not specified, the builder queries Azure for the appropriate value. If the builder cannot disambiguate the value, a value must be provided for this setting.	10 years ago