Tom Harvey

ping @zizw123

@navba-MSFT @myc2h6o looks like the original FR in this PR is still valid/unfixed, however - so shouldn't this remain open until it's fixed?

@JeffreyRichter > PATCH can be used for create as well as for update. To be honest as a consumer of the API / Swagger/OpenAPI Definitions to be honest that's concerning...

@Flasheh unfortunately I think this is more of a Core UX issue than something specific to the Backend unfortunately. The reasoning for this warning is that this feature-flag is a...

> @tombuildsstuff do you see the equivalent argument in the Azure provider behaving in the same way? By which I mean: generating the warning even if the user didn't actually...

hi @dc232 Thanks for opening this issue. As you've mentioned the field `host_name` is available which (I'd agree is unclear) does contain the FQDN here (e.g. `{contoso}.azureedge.net`) - so it...

Closing [since per this comment](https://github.com/hashicorp/terraform-provider-azurerm/issues/15144#issuecomment-1105896225) this was released in v3.4.0

Closing since this appears to have been [fixed in v3.14.0](https://github.com/hashicorp/terraform-provider-azurerm/pull/17556)

Agreed - this is a bug, presumably we should be removing these modules by default then allowing users to re-add them using the resources at the specific version they're expecting;...

@mikemadeja apologies, yeah this was released in v3.4.0 ([per the comment you've linked above](https://github.com/hashicorp/terraform-provider-azurerm/issues/8481#issuecomment-1105896526)) - closing this out.