Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metadata validation in azurerm_storage_container is more restrictive then azure portal #20737

Open
1 task done
daniel-anova opened this issue Mar 2, 2023 · 3 comments
Open
1 task done
Labels
bug sdk/requires-upgrade This is dependent upon upgrading an SDK service/storage v/3.x

Comments

@daniel-anova
Copy link
Contributor

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

Terraform Version

1.3.9

AzureRM Provider Version

3.35.0

Affected Resource(s)/Data Source(s)

azurerm_storage_container

Terraform Configuration Files

resource "azurerm_resource_group" "example" {
  name     = "example-resources"
  location = "West Europe"
}

resource "azurerm_storage_account" "example" {
  name                     = "examplestoraccount"
  resource_group_name      = azurerm_resource_group.example.name
  location                 = azurerm_resource_group.example.location
  account_tier             = "Standard"
  account_replication_type = "LRS"

  tags = {
    environment = "staging"
  }
}

resource "azurerm_storage_container" "example" {
  name                  = "container"
  storage_account_name  = azurerm_storage_account.example.name
  container_access_type = "private"

  metadata = {
    myKey = "value"
  }
}

Debug Output/Panic Output

N/A

Expected Behaviour

camelCase names should be allowed for key names.

Actual Behaviour

terraform enforces all lowercase as per changes done in #10723

Steps to Reproduce

  1. terraform apply

Important Factoids

No response

References

Key case was enforced to lowercase by #10723, however in the Portal it's possible to create upper case labels.

@github-actions github-actions bot removed the bug label Mar 2, 2023
@magodo magodo added bug sdk/requires-upgrade This is dependent upon upgrading an SDK labels Mar 3, 2023
@magodo
Copy link
Collaborator

magodo commented Mar 3, 2023

The issue resides in the go-autorest:

r.Header.Set(http.CanonicalHeaderKey(name), value)

@magodo
Copy link
Collaborator

magodo commented Mar 22, 2023

@tombuildsstuff Do we have a plan to migrate the transport layer for giovanni, given go-autorest seems not going to fix: Azure/go-autorest#721

@tombuildsstuff
Copy link
Contributor

@magodo see tombuildsstuff/giovanni#71, tombuildsstuff/giovanni#68 and tombuildsstuff/giovanni#75

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug sdk/requires-upgrade This is dependent upon upgrading an SDK service/storage v/3.x
Projects
None yet
Development

No branches or pull requests

4 participants