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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

azurerm_resource_provider_registration "Microsoft.Compute" always updates the resource despite no changes made #25752

Open
1 task done
mruepp opened this issue Apr 25, 2024 · 2 comments

Comments

@mruepp
Copy link

mruepp commented Apr 25, 2024

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

AzureRM Provider Version

3.97.1

Affected Resource(s)/Data Source(s)

azurerm_resource_provider_registration

Terraform Configuration Files

locals {
  common_resource_providers      = toset([
                                    "Microsoft.Storage",
                                    "Microsoft.Compute",
                                    "Microsoft.KeyVault",
                                    "Microsoft.Kubernetes",
                                    "Microsoft.Network",
                                    "Microsoft.DevTestLab",
                                  ])

}

resource "azurerm_resource_provider_registration" "logmon" {
  for_each  = var.ISPRD || var.ISINT ? local.common_resource_providers : []
  name      = each.key
}

Debug Output/Panic Output

# azurerm_resource_provider_registration.logmon["Microsoft.Compute"] will be updated in-place
  ~ resource "azurerm_resource_provider_registration" "logmon" {
        id   = "/subscriptions/<REDACTED>/providers/Microsoft.Compute"
        name = "Microsoft.Compute"

      - feature {
          - name       = "FastPathForced_uswestcentral" -> null
          - registered = false -> null
        }
    }

Expected Behaviour

The resource provider should not change anything because we never introduced the feature:

      - feature {
          - name       = "FastPathForced_uswestcentral" -> null
          - registered = false -> null
        }

wether via terraform nor via Azure Gui config or something else.

Actual Behaviour

Despite the provider was registered, each run of the tf conf reconfigures the following:

      - feature {
          - name       = "FastPathForced_uswestcentral" -> null
          - registered = false -> null
        }

This results in extremely long runs because the reconfiguring of the Resource providers results in 20-30min runs.

Why is the feature enabled anyway? Our location is switzerlandnorth and we never use the uswestcentral region:

      - feature {
          - name       = "FastPathForced_uswestcentral" -> null
          - registered = false -> null
        }

Steps to Reproduce

Configure subscription resource providers via terraform
Rerun the terraform plan/apply. The feature gets introduced without defining it.

Important Factoids

Region is Switzerlandnorth

References

No response

@aochsner
Copy link
Contributor

FWIW seeing the same behavior today.

TF Version 1.5.1
Provider version 3.91.0

Strongly suspecting something on the MSFT side...

@pranabpm
Copy link

My Cx is seeing same issue and its taking them > 16min without any changes to their code. Is there an active case registered that MSFT team is working on? Interested to get an update on potential fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants