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

Please add the ability to change the resource mode and apply a log analytics workspace ID to azurerm_application_insights #25533

Closed
jwshive opened this issue Jul 9, 2020 · 2 comments

Comments

@jwshive
Copy link

jwshive commented Jul 9, 2020

Current Terraform Version

Terraform v0.12.25
+ provider.azurerm v2.17.0

Use-cases

I am attempting to bind a new application insights resource to a pre-existing log analytics workspace for log consolidation and query.

Attempted Solutions

I attempted to look through the Terraform documentation for how to change Resource mode from classic to workspace-based (which is in tech preview) but there appears to currently be no such option.

Proposal

Extend the azurerm_application_insights resource to allow for a resource_mode directive which would allow for a no options classic mode (today) and a workspace-based option which would take in the current subscription and the id of the log analytics workspace.

References

@ghost
Copy link

ghost commented Jul 9, 2020

This issue has been automatically migrated to hashicorp/terraform-provider-azurerm#7667 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#7667.

@ghost
Copy link

ghost commented Aug 9, 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 Aug 9, 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