Martin Atkins

Hi @Flasheh! Thanks for reporting this. Do you think that what you are seeing is one warning for the backend configuration and one warning for the provider configuration? Those are...

`terraform_remote_state` also configures the backend in the same way, so indeed it seems plausible to me that some of them are coming from there. The Azure provider team maintains all...

Thanks for that extra context, @tombuildsstuff. I hadn't understood from the initial writeup that the backend is producing that error warning even if the argument isn't set _at all_; that...

I did some initial digging into both SDKv2 and the older version of it we have embedded in Terraform to support these not-yet-updated backends. It looks like both of them...

Indeed, it does seem like there are two bugs to address here, though I would hesitate to split this just yet unless we move ahead with solving only one of...

The forthcoming v1.3.0 release includes the end of the deprecation period for Azure AD Graph and so this option (including the deprecation warning) will be removed entirely in that version,...

FWIW that `host` block is there primarily for us to do development and is potentially risky to use for other purposes because it will entirely override the services for a...

Sorry for not reading clearly and assuming you were talking about providers. As some context for others reading, there was a parallel discussion about this with @jamengual in the HangOps...

As a general rule we do not offer any customization options for `terraform fmt`, because its purpose is to represent the standard formatting that all Terraform configuration should ideally follow....

Hi @orgads! Thanks for reporting this. Unfortunately I think this request is kinda against the principle of the "forced abort" functionality: the intent here is to drop everything and immediately...