jackofallops

Hi @harshavmb - Thanks for this PR. This block has been deprecated due to a circular reference problem and replaced with a new resource `azurerm_container_app_custom_domain`. We're investigating the support of...

Hi @adamyager - This isn't in scope for the service rewrite currently as we don't support provisioning Functions (within a Function App / Static Web App) at this time (which...

Thanks for the feedback @adamyager - apologies if my reply came across a little terse, that wasn't the intention 🙈 Apparently I missed the GA on the BYOF feature, I...

Hi All :wave: We’re still looking to support this functionality, however we require acceptance tests for each resource that the Azure Provider supports and due to the way that the...

Tests passing: 

> @tombuildsstuff Thanks for the comment, adding the empty check for this property. Tests are fine:  Hi @xiaxyi - Can you take a look at optimising the test config,...

> @jackofallops The PR is rebased on your latest changes to the eventhub test cases. Would you mind taking a look? Thanks Hi @xiaxyi - Looks like there's another error...

*bump* - Is someone available to triage and respond to this? This apparent breaking change is blocking feature adoption and development in the Terraform AzureAD provider.

Thanks for the reply @baywet. Our ingestion of the data expects a 2-part path for the tags, as seems to be the standard for every other tag in the spec....

Apologies for missing this one, this was closed by https://github.com/hashicorp/terraform-provider-azurerm/pull/29871 ```bash export ARM_MSI_API_VERSION="2019-08-01" # optional, defaults to 2018-02-01. Some Azure services require a newer API version due to local implementation...