Bump Azure/azapi from 1.12.1 to 1.13.1 in /src/infra/workload/releaseunit

[dependabot]

Bumps Azure/azapi from 1.12.1 to 1.13.1.

Release notes

Sourced from Azure/azapi's releases.

v1.13.1

ENHANCEMENTS:

• 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.

BUG FIXES:

• Fix a bug when upgrading from previous provider azapi_resource resource will set tags and location for resources that don't have tags or location in the configuration.
• Fix a bug that azapi_resource resource cannot handle tags with unknown values.
• Fix a bug that null string value can't pass the schema validation.
• Fix a bug that required fields which have null value can't pass the schema validation.
• Fix a bug that schema validation fails to validate the float number in the body.
• Fix a bug that client certificate authentication doesn't work.
• Fix a bug that auxiliary tenant ids are not passed to the client.
• Fix a bug that azapi_resource_action resource shows the plan diff when upgrading from the previous provider.

v1.13.0

BREAKING CHANGES:

1. Provider field 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.
2. The 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.
3. Defining the 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.
4. azapi_resource data source, azapi_resource_listdata source: Theoutput` 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:
   1. Please remove the 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
   }

   2. Run terraform plan to preview the changes.

   No changes. Your infrastructure matches the configuration.
   

ENHANCEMENTS:

• 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_pathand client_secret_file_path fields, which are used to specify the file path of the client id and client secret.

... (truncated)

Changelog

Sourced from Azure/azapi's changelog.

v1.13.1 (Unreleased)

ENHANCEMENTS:

• 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.

BUG FIXES:

• Fix a bug when upgrading from previous provider azapi_resource resource will set tags for resources that don't have tags in the configuration.
• Fix a bug that azapi_resource resource cannot handle tags with unknown values.
• Fix a bug that null string value can't pass the schema validation.
• Fix a bug that required fields which have null value can't pass the schema validation.
• Fix a bug that schema validation fails to validate the float number in the body.
• Fix a bug that client certificate authentication doesn't work.
• Fix a bug that auxiliary tenant ids are not passed to the client.
• Fix a bug that azapi_resource_action resource shows the plan diff when upgrading from the previous provider.

v1.13.0

BREAKING CHANGES:

• Provider field 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.
• The 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.
• Defining the 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: 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.

ENHANCEMENTS:

• 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_pathand 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.
• Update bicep types to ms-henglu/bicep-types-az@48ce933

BUG FIXES:

• Fix a bug that azapi_resource_action doesn't support 204 status code as a success response.

Commits

• c33ba00 improve the dynamic converter to distinguish null list and empty list (#485)
• 1dc49e4 increase the test timeout
• 48f26e6 bugfix: required fields with null value failed to pass validation (#484)
• fedc710 add upgrade tests to detect breaking changes (#474)
• bc38e6b azapi: Support enable_hcl_output_for_data_source field (#481)
• 9485028 bugfix: client certificate authentication doesn't work (#479)
• dcdb423 bugfix: skip validating the float number in the body (#469)
• 3afdfe2 bugfix: skip setting empty tags in request body (#466)
• 34332a3 bugfix: azapi_resource cannot handle tags with unknown values (#471)
• 1bdb8df bugfix: null value can't pass schema validation (#465)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once it's up-to-date and CI passes on it, as requested by @heoelri.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[heoelri]

@dependabot merge