Open kewalaka opened 7 months ago
Feature Request
0.1.2
No response
When specifying log analytics, it is necessary to specify both the customer ID and customer key.
This is because we are using AzAPI under the hood, and that appears to be the requirement there
https://learn.microsoft.com/en-us/azure/templates/microsoft.app/managedenvironments?pivots=deployment-language-terraform#loganalyticsconfiguration-2
It is not clear from the docs if the key is optional
By comparison, when using AzureRM, only the workspace ID is required:
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/container_app_environment#log_analytics_workspace_id
This is preferable, as it avoids have to fetch & pass the LAW key.
have a fix in testing (linked above) that i'm hoping will address this.
Check for previous/existing GitHub issues
Module specific issue
Issue Type?
Feature Request
(Optional) Module Version
0.1.2
(Optional) Correlation Id
No response
Description
When specifying log analytics, it is necessary to specify both the customer ID and customer key.
This is because we are using AzAPI under the hood, and that appears to be the requirement there
https://learn.microsoft.com/en-us/azure/templates/microsoft.app/managedenvironments?pivots=deployment-language-terraform#loganalyticsconfiguration-2
It is not clear from the docs if the key is optional
By comparison, when using AzureRM, only the workspace ID is required:
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/container_app_environment#log_analytics_workspace_id
This is preferable, as it avoids have to fetch & pass the LAW key.