Closed lra closed 2 years ago
Hey @lra, apologies for the regression here. We got a fix in with #17755 and just pushed a release out to 3.15.1. Let me know if that fixes up this issue for you!
Same problem with 3.15.1 can you reopen this? See:
- Installing hashicorp/azurerm v3.15.1...
- Installed hashicorp/azurerm v3.15.1 (signed by HashiCorp)
│ Error: parsing "/subscriptions/SOME_ID/resourceGroups/smc-prod-eastus/providers/Microsoft.DBForPostgreSQL/servers/_SOME_SERVER/databases/SOME_DATABASE": parsing segment "staticMicrosoftDBforPostgreSQL": expected the segment "Microsoft.DBForPostgreSQL" to be "Microsoft.DBforPostgreSQL"
│
│ with module.stack.azurerm_postgresql_database.this["engagement-taskqueue"],
│ on ../../modules/***-az-stack/postgresql.tf line 204, in resource "azurerm_postgresql_database" "this":
│ 204: resource "azurerm_postgresql_database" "this" {
I guess the problem is now on azurerm_postgresql_database
and has been fixed for azurerm_postgresql_server
. Want me to open a new ticket instead?
That'd be great! I imagine you've got quite a few oddities. Can you look through your all your postgres resource ids and see which resources are using Microsoft.DBForPostgreSQL
instead of Microsoft.DBforPostgreSQL
in their IDs?
New issue: https://github.com/hashicorp/terraform-provider-azurerm/issues/17763
I tried, and we exclusively have lowercase Microsoft.DBforPostgreSQL
, no Microsoft.DBForPostgreSQL
(big F) at all.
e.g. in one single region with a dumped state file:
$ rg DBforPostgreSQL terraform.tfstate|wc -l
2210
$ rg DBForPostgreSQL terraform.tfstate|wc -l
0
Same in a few other regions, so I stopped looking.
This functionality has been released in v3.16.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.
For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!
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.
Is there an existing issue for this?
Community Note
Terraform Version
1.2.5
AzureRM Provider Version
3.15.0
Affected Resource(s)/Data Source(s)
azurerm_postgresql_server
Terraform Configuration Files
Debug Output/Panic Output
$ terraform plan No changes. Your infrastructure matches the configuration.
Steps to Reproduce
terraform plan
Important Factoids
It works with v3.14.0
References
No response