Martin Atkins

Hi @novtor! Thanks for reporting this. The behavior you described here seems similar to another bug we fixed in a later version of Terraform than the one you are currently...

Thanks for confirming, @novtor! Unfortunately when I tried to access the logs link you included in your comment I got a 404 error. Have you deleted the gist that you...

It does seem like there is a mixture of things here and so it's not clear yet which is the root cause, but we can see for certain that Terraform...

Hi @mpigram, For the Azure provider error in particular, it could be that the particular version of the Azure provider you are using is compiled in such a way that...

Hi @mpigram, I'm unfortunately not a macOS user myself and so I've been struggling a little to try to prove either way whether my theory about the cause of the...

If the provider's macOS releases are cross-compiled from Linux then I think golang/go#12524 is the most likely root cause here: unless taking some very unusual steps in the build process...

Thanks for confirming, @tombuildsstuff. At this point then it seems like what remains for this issue is to determine why this problem appeared as the "Plugin did not respond" error,...

Hi again @mpigram! We didn't hear back from you after the request to try this with AzureRM Provider 3.1.0, so I'm going to close this under the assumption that this...

Hi @ewbankkit, This sort of validation is typically more the responsibility of the SDK than of Terraform Core, because Terraform Core must generally be compatible with providers written at various...

Revisiting this some time later, I think I'm going to close this because I don't think it's possible for us to retroactively start rejecting argument names that we previously accepted...