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_monitor_autoscale_setting - notifications - webhook - crashes terraform #24707

Closed
salsop opened this issue Apr 19, 2020 · 2 comments
Closed

Comments

@salsop
Copy link

salsop commented Apr 19, 2020

Terraform v0.12.24

  • provider.azurerm v2.6.0

When running this part of the plan Terraform crashes:

resource "azurerm_monitor_autoscale_setting" "ngfw" {
  name                = "vmss-settings-ngfw"
  resource_group_name = var.rgname
  location            = var.location
  target_resource_id  = azurerm_linux_virtual_machine_scale_set.ngfw.id
  profile {
    name = "NGFW Autoscale"
    capacity {
      default = var.instances
      minimum = var.instances
      maximum = 100
    }
  notification {
    webhook {
      service_uri = "https://autoscale-function-gusaylum.azurewebsites.net/api/infra?code=2wf8QecvVO3csMvf8EHQ0iLm/zQwna8zI3ol9cmUkUsuIztTmX7Eqg=="
    }
  }
}

If I remove this part of the plan, it executes as expected:

  notification {
    webhook {
      service_uri = "https://autoscale-function-gusaylum.azurewebsites.net/api/infra?code=2wf8QecvVO3csMvf8EHQ0iLm/zQwna8zI3ol9cmUkUsuIztTmX7Eqg=="
    }
  }

Expected Behavior

Should create Autoscale notification with Webhook

Actual Behavior

Terraform crashes

Steps to Reproduce

Run terraform with notification block, and terraform crashes.

@ghost
Copy link

ghost commented Apr 20, 2020

This issue has been automatically migrated to hashicorp/terraform-provider-azurerm#6543 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-azurerm#6543.

@ghost
Copy link

ghost commented May 21, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 21, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants