Terraform provider for Azure Resource Manager Rest API
azapi
provider: Support enable_hcl_output_for_data_source
field, which is used to enable the HCL output for the data source, the default value is false
.
This could resolve the following breaking changes in the previous release:
azapi_resource
data source: The output
field changes from JSON string to HCL object. Users can use access the fields in the output as an HCL object. Please remove the jsondecode
function when using the output
field.azapi_resource_list
data source: The output
field changes from JSON string to HCL object. Users can use access the fields in the output as an HCL object. Please remove the jsondecode
function when using the output
field.Please notice if you already upgraded to v1.13.0
and removed jsondecode
function for the output
of data sources, when upgrade to the v1.13.1
release, you need to set enable_hcl_output_for_data_source = true
in the azapi
provider block to enable the HCL output for data sources.
azapi_resource
resource will set tags
and location
for resources that don't have tags
or location
in the configuration.azapi_resource
resource cannot handle tags with unknown values.null
string value can't pass the schema validation.null
value can't pass the schema validation.azapi_resource_action
resource shows the plan diff when upgrading from the previous provider.default_naming_prefix
and default_naming_suffix
are deprecated. It will not work in this release and will be removed in the next major release.
Please specify the naming prefix and suffix in the resource's name
field instead.azapi_resource
's removing_special_chars
field is deprecated. It will not work in this release and will be removed in the next major release.
Please specify the name
field and remove the special characters in the name
field instead.identity
inside the body
field is not recommended. In this release, it will not sync the identity
inside the body
field to identity
block.
Please define the identity
block instead.azapi_resource
data source, azapi_resource_listdata source: The
output` field changes from JSON string to HCL object. Users can use access the fields in the output as an HCL object. Please follow the instructions to migrate:
jsondecode
function when using the output
field from these data sources.data "azapi_resource" "test" {
type = "Microsoft.Automation/automationAccounts@2023-11-01"
resource_id = azapi_resource.auto.id
response_export_values = ["properties"]
}
output "o1" {
// change jsondecode(data.azapi_resource.test.output).properties.automationHybridServiceUrl to
value = data.azapi_resource.test.output.properties.automationHybridServiceUrl
}
terraform plan
to preview the changes.No changes. Your infrastructure matches the configuration.
azapi_resource
resource, azapi_update_resource
resource, azapi_resource_action
resource, azapi_data_plane_resource
resource, azapi_resource_action
data source: The body
field supports the dynamic schema and allows user to use the HCL object to specify the body.azapi_resource
resource, azapi_update_resource
resource, azapi_resource_action
resource, azapi_data_plane_resource
resource, azapi_resource_action
data source, azapi_resource
data source, azapi_resource_list
data source: The output
field supports the dynamic schema and allows user to read the output as an HCL object.azapi
provider: Support client_id_file_path
and client_secret_file_path
fields, which are used to specify the file path of the client id and client secret.azapi_data_plane_resource
resource: Support Microsoft.Synapse/workspaces/databases
type.azapi_resource
resource, azapi_update_resource
resource: Ignore the order of the elements in a list if the element has a name
field as identifier.azapi_resource_action
doesn't support 204 status code as a success response.BUG FIXES:
azapi_resource
removes some required fields in the body
when using ignore_body_changes
feature.ENHANCEMENTS:
BUG FIXES:
ignore_body_changes
incorrectly removes tags.NOTICE:
default_naming_prefix
and default_naming_suffix
are deprecated. It will not work in the next minor release and will be removed in the next major release.
Please specify the naming prefix and suffix in the resource's name
field instead.azapi_resource
's removing_special_chars
field is deprecated. It will not work in the next minor release and will be removed in the next major release.
Please specify the name
field and remove the special characters in the name
field instead.identity
inside the body
field is not recommended. In the next minor release, it will not sync the identity
inside the body
field to identity
block.
Please define the identity
block instead.ENHANCEMENTS:
azapi_resource_action
resource: Support HEAD
method.azapi_resource_action
resource: Support when
field, which is used to control when to execute the action.ENHANCEMENTS:
azapi_resource
data source: When creating Microsoft.Resources/subscriptions
, resource_id
is optional and defaults to the ID of the default subscription.azapi
: Support endpoint
block, which is used to configure the endpoints of the Azure Clouds.azapi_resource_action
resource: Support GET
method.BUG FIXES:
body
is not set when import with an unrecognized api-version
.azapi_update_resource
resource.FEATURES:
ENHANCEMENTS:
azapi_resource
resource/data source: When creating Microsoft.Resources/resourceGroups
, parent_id
is optional and defaults to the ID of the default subscription.azapi_resource
resource: Support ignore_body_changes
field, which is used to ignore some properties when comparing the resource with its current state.azapi_update_resource
resource: Support ignore_body_changes
field, which is used to ignore some properties when comparing the resource with its current state.BUG FIXES:
azapi_resource
resource doesn't store the id
in the state when error happens during the creation.FEATURES:
ENHANCEMENTS:
azapi_resource_action
: Support provider action.BUG FIXES:
Microsoft.Resources/providers
is not parsed correctly.Microsoft.Resources/tenants
is not parsed correctly.FEATURES:
azapi
: Support use_msi
and use_cli
features.azapi
: Support auxiliary_tenant_ids
field, which is required for multi-tenancy and cross-tenant scenarios.azapi
: Support custom_correlation_request_id
field, which is used to specify the correlation request id.ENHANCEMENTS:
BUG FIXES:
FEATURES:
ENHANCEMENTS:
BUG FIXES: