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

App Config tags keeps re-applying since AzureRM v2.61 #12050

Closed
dhmoto17 opened this issue Jun 3, 2021 · 2 comments · Fixed by #12062
Closed

App Config tags keeps re-applying since AzureRM v2.61 #12050

dhmoto17 opened this issue Jun 3, 2021 · 2 comments · Fixed by #12062

Comments

@dhmoto17
Copy link

dhmoto17 commented Jun 3, 2021

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 (and AzureRM Provider) Version

Affected Resource(s)

  • azurerm_app_configuration

Expected Behaviour

No changes to app configuration resource

Actual Behaviour

Every run of terraform reports an planned change to tags.
It also randomly picks one of the current tag values and reports that as the value for all the tags, which it will change to what is expected in code.
When checking Azure the tags are as they should be according to the code (i.e. no changes should be planned)

azurerm_app_configuration.app_conf will be updated in-place
~ resource "azurerm_app_configuration" "app_conf" {
endpoint = "https://XXXX-appconfig.azconfig.io"
id = "/subscriptions/XXXX-dc49-4afe-8839-bfa2fc3fc974/resourceGroups/XXXX-appconfig-rg/providers/Microsoft.AppConfiguration/configurationStores/XXXX-appconfig"
location = "uksouth"
name = "XXXX-appconfig"
primary_read_key = [
{
connection_string = "Endpoint=https://XXXX-appconfig.azconfig.io;Id=XXXX;Secret=XXXX"
id = "XXXX"
secret = "XXXX"
},
]
primary_write_key = [
{
connection_string = "Endpoint=https://XXXX-appconfig.azconfig.io;Id=XXXX;Secret=XXXX"
id = "XXXX"
secret = "XXXX"
},
]
resource_group_name = "XXXX-appconfig-rg"
secondary_read_key = [
{
connection_string = "Endpoint=https://XXXX-appconfig.azconfig.io;Id=XXXX;Secret=XXXX"
id = "XXXX"
secret = "XXXX"
},
]

    ]
    secondary_write_key = [
        {
            connection_string = "Endpoint=https://XXXX-appconfig.azconfig.io;Id=XXXX;Secret=XXXX"
            id                = "XXXX"
            secret            = "XXXX"
        },
    ]
    sku                 = "standard"
  ~ tags                = {
      ~ "business_owner"        = "5m" -> "Platform"
      ~ "data_sensitivity"      = "5m" -> "High"
      ~ "docs_location"         = "5m" -> ""
      ~ "environment"           = "5m" -> "dev"
      ~ "function_of_component" = "5m" -> "Stores and manages application configuration"
      ~ "function_of_system"    = "5m" -> "Stores and manages application configuration"
      ~ "name_of_system"        = "5m" -> "Application Configuration"
      ~ "namespace_environment" = "5m" -> "XXXX"
      ~ "parent"                = "5m" -> "XXXX-appconfig-rg"
        "rto"                   = "5m"
      ~ "tech_owner"            = "5m" -> "Platform"
    }
}

Steps to Reproduce

terraform plan with code containing an app configuration resource.

Important Factoids

References

@ghost
Copy link

ghost commented Jun 11, 2021

This has been released in version 2.63.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.63.0"
}
# ... other configuration ...

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.