features

Documentation

Index

• func ShouldResourcesBeImported() bool
• func SupportsCustomTimeouts() bool
• func SupportsTwoPointZeroResources() bool
• func UseDynamicTestLocations() bool

Functions

func ShouldResourcesBeImported

func ShouldResourcesBeImported() bool

ShouldResourcesBeImported returns whether the feature Requiring Resources to be Imported should be enabled.

This feature prevents Terraform from 'adopting' resources which already exist, which is the behaviour used by ARM Templates which will update these resources rather than overwriting them Instead existing resources will need to be imported using `terraform import`, as is the case with other Terraform Providers.

This feature-toggle defaults to off in 1.x versions of the Azure Provider, however this will become the default behaviour in version 2.0 of the Azure Provider. As outlined in the announcement for v2.0 of the Azure Provider: https://github.com/terraform-providers/terraform-provider-azurerm/issues/2807

Operators wishing to adopt this behaviour can opt-into this behaviour in 1.x versions of the Azure Provider by setting the Environment Variable 'ARM_PROVIDER_STRICT' to 'true'

func SupportsCustomTimeouts

func SupportsCustomTimeouts() bool

SupportsCustomTimeouts returns whether Custom Timeouts are supported

This feature allows Resources to define Custom Timeouts for Creation, Updating and Deletion which helps work with Azure resources that take longer to provision/delete. When this feature is disabled, all resources have a hard-coded timeout of 3 hours.

This feature-toggle defaults to off in 1.x versions of the Azure Provider, however this will become the default behaviour in version 2.0 of the Azure Provider. As outlined in the announcement for v2.0 of the Azure Provider: https://github.com/terraform-providers/terraform-provider-azurerm/issues/2807

Operators wishing to adopt this behaviour can opt-into this behaviour in 1.x versions of the Azure Provider by setting the Environment Variable 'ARM_PROVIDER_CUSTOM_TIMEOUTS' to 'true'

func SupportsTwoPointZeroResources

func SupportsTwoPointZeroResources() bool

SupportsTwoPointZeroResources returns whether the new VM and VMSS resources from 2.0 should be supported

There's 5 new resources coming as a part of 2.0, which are intentionally feature-flagged off until all 5 are supported:

• `azurerm_linux_virtual_machine`
• `azurerm_linux_virtual_machine_scale_set`
• `azurerm_windows_virtual_machine`
• `azurerm_windows_virtual_machine_scale_set`
• `azurerm_virtual_machine_scale_set_extension`

This feature-toggle defaults to off in 1.x versions of the Azure Provider, however this will become enabled by default in version 2.0 of the Azure Provider (where this toggle will be removed). As outlined in the announcement for v2.0 of the Azure Provider: https://github.com/terraform-providers/terraform-provider-azurerm/issues/2807

Operators wishing to beta-test these resources can opt-into them in 1.x versions of the Azure Provider by setting the Environment Variable 'ARM_PROVIDER_TWOPOINTZERO_RESOURCES' to 'true'

func UseDynamicTestLocations

func UseDynamicTestLocations() bool

UseDynamicTestLocations returns whether or not the Acceptance Test data should use dynamic values for test locations

In practice this means that of the available test locations, the primary, secondary and ternary locations will change dynamically for each test

The primary benefit of this is to distribute the tests across Azure Regions, to improve the overall reliability. In time this'll become the default value.

It's possible to opt into this by setting `ARM_PROVIDER_DYNAMIC_TEST` to `true`.