The Wire · Showcase
TERRAFORM PROVIDER SURGE: AZURERM FIXES CRITICAL SQL MIGRATION, AWSCC SHIPS 35+ NEW RESOURCES
By RepoJournal · Filed · About HashiCorp
Azure's managed SQL instance now safely transitions between SKU tiers, while AWS CloudControl adds 35 new data sources and resources in a single release.
The terraform-provider-azurerm desk shipped a critical fix [1] that resolves an error when migrating SQL managed instances from General Purpose to Business Critical SKUs, a common upgrade path enterprises hit without warning. This lands alongside three other Azure refinements: deprecating the Essential SKU tier for Grafana dashboards [2], adding metrics monitoring to storage object replication [3], and fixing RabbitMQ scaling rules in container apps [4]. On the Vault policy front, terraform-provider-vault now prevents accidental overwrites of pre-existing policies during resource creation [5], a protection that should have existed from day one and now includes an allow_overwrite toggle for cases where you actually need it. The AWS CloudControl provider [6] shipped v1.88.0 with 35 new data sources and resources tracking the latest CloudFormation schema updates [7], including Bedrock agent payment managers and new resilience hub service functions. Over at Consul, the UI team removed the deprecated Slotted addon pattern [8] in favor of named blocks, a technical debt elimination that simplifies component architecture. Vault Enterprise pulled in a reporting dashboard migration from the shared package [9] and backported Cassandra certificate fixes [10] that were causing test failures with expired static certs.
Action items
- → Plan azurerm upgrade if you manage SQL instances transitioning between GP and BC SKUs [ref:7] hashicorp/terraform-provider-azurerm [plan]
- → Review vault_policy resource code if you auto-create policies; allow_overwrite defaults to false [ref:14] hashicorp/terraform-provider-vault [monitor]
- → Update AWS CloudControl provider to v1.88.0 if you use Bedrock or resilience hub resources [ref:15] hashicorp/terraform-provider-awscc [plan]
References
- [1] `azurerm_mssql_managed_instance` - ensure `isGeneralPurposeV2` is removed when changing to BC SKU (#32560) hashicorp/terraform-provider-azurerm
- [2] `azurerm_dashboard_grafana` deprecate the `Essential` value for the `sku` property (#32538) hashicorp/terraform-provider-azurerm
- [3] `azurerm_storage_object_replication` - Support `metrics_enabled` ↗ hashicorp/terraform-provider-azurerm
- [4] `azurerm_container_app` - fix rabbitmq scale rule metadata in acceptance test ↗ hashicorp/terraform-provider-azurerm
- [5] vault_policy do not overwrite pre-existing policies on create (#2895) hashicorp/terraform-provider-vault
- [6] v1.88.0 ↗ hashicorp/terraform-provider-awscc
- [7] 2026-06-10 Schema Updates ↗ hashicorp/terraform-provider-awscc
- [8] Remove Slotted addon ↗ hashicorp/consul
- [9] Backport Migrate Vault Reporting Dashboard from shared package into Vault Enterprise into ce/main (#15382) hashicorp/vault
- [10] tests: fix cassandra db test expired certs (#15381) (#15392) hashicorp/vault
FAQ
- What changed in HashiCorp on June 11, 2026?
- Azure's managed SQL instance now safely transitions between SKU tiers, while AWS CloudControl adds 35 new data sources and resources in a single release.
- What should HashiCorp teams do about it?
- Plan azurerm upgrade if you manage SQL instances transitioning between GP and BC SKUs [ref:7] • Review vault_policy resource code if you auto-create policies; allow_overwrite defaults to false [ref:14] • Update AWS CloudControl provider to v1.88.0 if you use Bedrock or resilience hub resources [ref:15]
- Which HashiCorp repositories shipped on June 11, 2026?
- hashicorp/terraform-provider-azurerm, hashicorp/terraform-provider-vault, hashicorp/terraform-provider-awscc, hashicorp/consul, hashicorp/vault