Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.12.1
->2.2.0
Release Notes
Azure/terraform-provider-azapi (azapi)
v2.2.0
Compare Source
ENHANCEMENTS:
azapi_resource
resource: Improved 403 handling for management group resources to include child resourcesBUG FIXES:
Notice: Terraform will detect the
output
field's changes made outside of Terraform since the last "terraform apply". You can runterraform refresh
to update the state file with the latest values.v2.1.0
Compare Source
FEATURES:
azapi_resource
resource: Support resource move operation, it allows moving resources fromazurerm
provider.ENHANCEMENTS:
azapi_client_config
data source: Supportobject_id
field.BUG FIXES:
body
contains an unknown float number, the provider will crash.v2.0.1
Compare Source
BREAKING CHANGES:
azapi_resource
,azapi_update_resource
resources and data sources'output
field defaults to the readonly fields when theresponse_export_values
is not specified.azapi_resource_list
data source'soutput
field defaults to the response when theresponse_export_values
is not specified.ENHANCEMENTS:
azapi_data_plane_resource
resource: SupportMicrosoft.Purview/accounts/Scanning/managedvirtualnetworks
type.azapi
provider: Supportdisable_default_output
field, which is used to disable the default output for the resources and data sources.BUG FIXES:
v1.15.0
Compare Source
ENHANCEMENTS:
BUG FIXES:
resource_id
andtype
fields are different.v1.14.0
Compare Source
FEATURES:
ENHANCEMENTS:
azapi
provider: Supportclient_certificate
field, which specifies base64-encoded PKCS#12 bundle to be used as the client certificate for authentication.azapi
provider: Supportuse_aks_workload_identity
field to enable AKS workload identity.azapi_resource
,azapi_update_resource
,azapi_resource_action
,azapi_data_plane_resource
resources: Supporttimeouts.update
field, which is used to specify the timeout for the update operation.azapi_update_resource
resource: Improve the id build logic to honor user's input.BUG FIXES:
azapi_resource
will crash when thelocation
in GET response is null.azapi_resource
only supports extension resource on a resource group scoped resource.v1.13.1
Compare Source
ENHANCEMENTS:
azapi
provider: Supportenable_hcl_output_for_data_source
field, which is used to enable the HCL output for the data source, the default value isfalse
.This could resolve the following breaking changes in the previous release:
azapi_resource
data source: Theoutput
field changes from JSON string to HCL object. Users can use access the fields in the output as an HCL object. Please remove thejsondecode
function when using theoutput
field.azapi_resource_list
data source: Theoutput
field changes from JSON string to HCL object. Users can use access the fields in the output as an HCL object. Please remove thejsondecode
function when using theoutput
field.BUG FIXES:
azapi_resource
resource will settags
for resources that don't havetags
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.v1.13.0
Compare Source
BREAKING CHANGES:
default_naming_prefix
anddefault_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
'sremoving_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 thename
field instead.identity
inside thebody
field is not recommended. In this release, it will not sync theidentity
inside thebody
field toidentity
block.Please define the
identity
block instead.azapi_resource
data source: Theoutput
field changes from JSON string to HCL object. Users can use access the fields in the output as an HCL object. Please remove thejsondecode
function when using theoutput
field.azapi_resource_list
data source: Theoutput
field changes from JSON string to HCL object. Users can use access the fields in the output as an HCL object. Please remove thejsondecode
function when using theoutput
field.ENHANCEMENTS:
azapi_resource
resource,azapi_update_resource
resource,azapi_resource_action
resource,azapi_data_plane_resource
resource,azapi_resource_action
data source: Thebody
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: Theoutput
field supports the dynamic schema and allows user to read the output as an HCL object.azapi
provider: Supportclient_id_file_path
andclient_secret_file_path
fields, which are used to specify the file path of the client id and client secret.azapi_data_plane_resource
resource: SupportMicrosoft.Synapse/workspaces/databases
type.azapi_resource
resource,azapi_update_resource
resource: Ignore the order of the elements in a list if the element has aname
field as identifier.BUG FIXES:
azapi_resource_action
doesn't support 204 status code as a success response.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.