Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

azurerm_application_insights - failure on create or update actions #1762

Closed
willgarcia opened this issue Aug 14, 2018 · 4 comments · Fixed by #1769
Closed

azurerm_application_insights - failure on create or update actions #1762

willgarcia opened this issue Aug 14, 2018 · 4 comments · Fixed by #1769

Comments

@willgarcia
Copy link

willgarcia commented Aug 14, 2018

It seems that the App insights Terraform resource is failing to create the corresponding Azure resource, possibly due to an uncontrolled change introduced in the Azure APIs.

The same resource using the ARM format can be created successfully:

...
        {
            "type": "microsoft.insights/components",
            "name": "myappinsights",
            "apiVersion": "2015-05-01",
            "location": "Southeast Asia",
            "kind": "web",
            "properties": {
              "Application_Type": "web"
            }
        }
...

Terraform Version

Terraform v0.11.7
Terraform Azure provider 1.12.0

Affected Resource(s)

azurerm_application_insights

Terraform Configuration Files

resource "azurerm_application_insights" "test" {
  name                = "myappinsights"
  resource_group_name = "mygroup"
  location            = "Southeast Asia"
  application_type    = "Web"
}

Output

* azurerm_application_insights.test: insights.ComponentsClient#CreateOrUpdate: Failure responding to request: StatusCode=201 -- Original Error: autorest/azure: Service returned an error. Status=201 Code="Unknown" Message="Unknown service error" Details=...
@tombuildsstuff
Copy link
Contributor

hey @willgarcia

Thanks for opening this issue :)

Taking a quick look into this I can confirm there's a breaking change here which has been made to the API which doesn't match what the SDK supports (either in the version of the SDK that we're using, or the latest version) - but I'll look into what we can do about fixing this today.

Thanks!

@tombuildsstuff
Copy link
Contributor

hey @willgarcia

Just to give an update here - I've opened #1769 which includes a fix for this which will go out in the next release of the Provider.

Thanks!

@willgarcia
Copy link
Author

willgarcia commented Aug 16, 2018

Hi @tombuildsstuff, thanks a lot for the fix and new release 1.13.0!

Good to know that we can track this type of issues on the Azure sdk github repo as well, by checking the Swagger spec :) I initially came across the HTTP 201 response code (with TF_LOG=debug) but could not confirm if it was an Azure API change or not.

Thanks

@ghost
Copy link

ghost commented Mar 30, 2020

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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants