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

Terraform crashes when linking an Azure Automation Account to a Log Analytics Workspace #4132

Closed
ghost opened this issue Aug 21, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Aug 21, 2019

This issue was originally opened by @sladeedmonds as hashicorp/terraform#22547. It was migrated here as a result of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.12.6

Terraform Configuration Files

resource "azurerm_log_analytics_workspace" "log_analytics_workspace_default" {
  name                = "${var.default_prefix}DefaultWorkspace${var.default_suffix}"
  location            = azurerm_resource_group.resource_group_log_analytics_workspaces.location
  resource_group_name = azurerm_resource_group.resource_group_log_analytics_workspaces.name
  sku                 = "PerGB2018"
  retention_in_days   = 30

  tags = var.tags
}

resource "azurerm_log_analytics_linked_service" "log_analytics_linked_service_azure_automation" {
  resource_group_name = azurerm_resource_group.resource_group_log_analytics_workspaces.name
  workspace_name = azurerm_log_analytics_workspace.log_analytics_workspace_default.name
}

Debug Output

Crash Output

https://gist.github.com/sladeedmonds/f1b650bdc2249acce810f8c69d39bead

Expected Behavior

Existing Azure Automation account should be linked to the Log Analytics Workspace.

Actual Behavior

Terraform crashed.

Steps to Reproduce

  1. terraform apply

Additional Context

References

@mbfrahry
Copy link
Member

Hey @sladeedmonds. Found the crash and the fix has been merged into the provider. It should be available when we release the provider. Thanks for taking the time to open this issue and let us know if you continue to see in this problem in the next released provider

@ghost
Copy link
Author

ghost commented Sep 28, 2019

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!

@ghost ghost locked and limited conversation to collaborators Sep 28, 2019
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

1 participant