2.6.1 introduced a bug in the error_message_regex

[ronaldvb-k]

Version 2.6.1 introduced an issue with error_message_regex retry parameter.

We have a generic TF module to create runCommands using the Microsoft.HybridCompute/machines/runCommands API.

In the module, the error_message_regex parameter is a empy list of strings by default (see below). But in some cases we have to specify an error messages, that's why it's variable.

  retry = {
    error_message_regex = try(each.value.retry.error_message_regex, [""])
  }

This worked fine in version 2.5, but since we upgraded to 2.6.1 we noticed that the creation always fails (hitting the 30m creation timeout).

In the debug logging, we noticed that the error_message_regex is always matched because both the error message and regex are empty.

2025-09-01T12:44:10.929+0200 [DEBUG] provider.terraform-provider-azapi_v2.6.1:  matches regex
2025-09-01T12:44:10.929+0200 [DEBUG] provider.terraform-provider-azapi_v2.6.1: [DEBUG] Sep  1 12:44:10.928984 Retry: End Try #3, Delay=15s
2025-09-01T12:44:25.934+0200 [DEBUG] provider.terraform-provider-azapi_v2.6.1: [DEBUG] Sep  1 12:44:25.934171 Retry: =====> Try=4 for PUT https://management.azure.com/subscriptions/xxxx/resourceGroups/rg-xxxx/providers/Microsoft.HybridCompute/machines/vm-xxx/runCommands/command-xxx?api-version=2024-07-31-preview
2025-09-01T12:44:25.934+0200 [DEBUG] provider.terraform-provider-azapi_v2.6.1: [DEBUG] Sep  1 12:44:25.934572 Request: ==> OUTGOING REQUEST (Try=4)

[matt-FFFFFF]

@ronaldvb-k what happens if you set the error_message_regex to null instead of a list with an empty string?

error_message_regex = try(each.value.retry.error_message_regex, null)

[ronaldvb-k]

@ronaldvb-k what happens if you set the error_message_regex to null instead of a list with an empty string?

error_message_regex = try(each.value.retry.error_message_regex, null)

Then we get a different error saying that the retry.error_message_regex is required:

│ Error: Missing Configuration for Required Attribute
│ 
│ Must set a configuration value for the retry.error_message_regex attribute as the provider has marked it as required.
│ 
│ Refer to the provider documentation or contact the provider developers for additional information about configurable attributes that are required.

[ms-henglu]

Hi @ronaldvb-k ,

How about removing the retry block? Because it's not used?

[matt-FFFFFF]

Like this:

  retry = can(each.value.retry.error_message_regex) ? {
    error_message_regex = each.value.retry.error_message_regex
  } : null