APIM Named Value Display Name unexpected validation error

[alexwiese]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.7.3

AzureRM Provider Version

3.91.0

Affected Resource(s)/Data Source(s)

azurerm_api_management_named_value

Terraform Configuration Files

resource "azurerm_api_management_named_value" "example" {
  name                = "example-apimg"
  resource_group_name = azurerm_resource_group.example.name
  api_management_name = azurerm_api_management.example.name
  display_name        = "ExampleProperty"
  value               = "Example Value"
}

Debug Output/Panic Output

│ Error: "display_name" may only contain alphanumeric characters, periods, underscores and dashes
│
│   with azurerm_api_management_named_value.example,
│   on mian.tf line 5, in resource "azurerm_api_management_named_value" "example":
│    5:   display_name        = "ExampleProperty"
│

Expected Behaviour

No validation error is returned, the named value is deployed successfully.

Actual Behaviour

Validation error is raised, the named value is not deployed successfully.

Steps to Reproduce

• terraform apply

Important Factoids

Issue only started with v3.91.0 of the provider. Appears to be introduced by #24749

References

No response

[rikribbers]

Same issue here; I did reproduce with version 3.90.0 and terraform plan was succesful so it was introduced in the latest release (3.91.0)

[alexwiese]

I’ve raised PR #24832 to fix this

[rdhaundiyalf5]

i have started getting same error in my application . what version am i supposed to change, it was working perfectly fine till day before yesterday

[alexwiese]

@rdhaundiyalf5 you can pin the version of azurerm to 3.90.0

terraform {
  required_providers {
    azurerm = {
      source = "hashicorp/azurerm"
      version = "3.90.0"
    }
  }
}

The issue should be fixed in v3.92.0 once it’s released.

[rdhaundiyalf5]

Thanks @alexwiese , i did that already and it started working. Earlier I was trying with v3.92.0 as I thought it was released

[hoaza]

We use a pipeline that always uses the latest version of terraform and azurerm. Does anyone have any ideas other than limiting the display_name to one character and waiting for the new version to be distributed?

[sushmitapandey]

My code also picks the latest terraform version and I am still getting the same error. Can anyone please help me with the ETA. when is it going to be fixed and what version should I use? I have already tried 3.90 and 3.91 but no luck.

[jussiheinonen]

Ran into same issue with version 3.91.0 provider. Downgraded provider version to 3.90.0 and plan/apply is working fine again.
Be explicit with the version statement version = "3.90.0" not version = ">= 3.90.0" to prevent Terrraform using the cached 3.91.0 provider from the previous run.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.