You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
locked and limited conversation to collaborators
Aug 9, 2020
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Terraform Version
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
The text was updated successfully, but these errors were encountered: