AppInsights: working around a breaking API change.

[tombuildsstuff]

The Application Insights API has started returning a HTTP 201 instead of a HTTP 200 (as is documented in the Swagger and thus used in the SDK) from ~2018-08-14 onwards; this PR works around this issue - which has been raised with MS here: Azure/azure-sdk-for-go#2465

Fixes #1762

[tombuildsstuff]

Tests pass:

[liamfoneill]

How do we start using this straight away? The App Insights API change a big breaking change for our env and we need to start using a provider with this PR asap. Do we have to wait until 1.13 or can you release a bug fix version of the provider?

[tombuildsstuff]

@liamfoneill as this is a breaking change we'll be doing a release later today - should you need to do this in the meantime you can compile the provider from source (details are in the README) - there's also an upstream change requesting the API's rolled back here:
Azure/azure-sdk-for-go#2465

[liamfoneill]

Great thank you Tom. I shall await the release

[tombuildsstuff]

hi @liamfoneill @scotm-gxg

Just to let you know that a fix for this issue has been released as part of v1.13.0 of the AzureRM Provider :)

Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!