Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
686 questions
Azure Container Apps Environment not setting daprAIConnectionString nor daprAIInstrumentationKey using azure cli or PoweShell
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 27%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFT%3C/text%3E%3C/svg%3E)
Francisco Tineo Mateo
0
Reputation points
We're deploying an Azure Container Application Environment and trying to setup the Dapr Connection String and Dapr Instrumentation Key. We get the same outcome whether we create using the az cli (version 2.66.0) command, PowerShell or Terraform.
PowerShell command:
New-AzContainerAppManagedEnv `
-ResourceGroupName "<ResourceGroupName>" `
-Location "<Location>" `
-Name "<EnvironmentName>" `
-DaprAiConnectionString "<DaprAiConnectionString>" `
-DaprAiInstrumentationKey "<DaprAiInstrumentationKey>" `
-VnetConfigurationInternal `
-WorkloadProfile $workloadProfile `
-VnetConfigurationInfrastructureSubnetId "<InfrastructureSubnetId>"
Azure CLI command:
az containerapp env create `
-g <ResourceGroupName> `
-l <Location> `
-n <EnvironmentName> `
-w `
--logs-workspace-id "<LogsWorkspaceId>" `
-d $APP_INSIGHTS_CONNECTION_STRING `
--dapr-instrumentation-key $APP_INSIGHTS_INSTRUMENTATION_KEY `
--internal-only true `
--logs-destination log-analytics `
-s "/subscriptions/<SubscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Network/virtualNetworks/<VirtualNetworkName>/subnets/<SubnetName>"
Azure Container Apps
{count} votes
-
James Hamil 27,211 Reputation points Microsoft Employee Moderator2024-11-14T01:10:51.6633333+00:00 Hi @Francisco Tineo Mateo , we are investigating your issue and will update you shortly.
Best,
James
-
LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator2024-11-14T01:23:05.5433333+00:00 Hi @Francisco Tineo Mateo Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.
Looking at the documentation of the latest version of Azure CLI, az containerapp env create command does support a parameter where you can pass in the Application Insights connection string. Please refer the parameter
--dapr-connection-stringthrough which you can configure this parameter. Below is a sample command to pass in the connection string.# Get the Log Analytics workspace customer ID and shared key WORKSPACE_ID=$(az monitor log-analytics workspace show --resource-group myResourceGroup --workspace-name myWorkspace --query customerId --output tsv) WORKSPACE_KEY=$(az monitor log-analytics workspace get-shared-keys --resource-group myResourceGroup --workspace-name myWorkspace --query primarySharedKey --output tsv) # Get the Application Insights connection string CONNECTION_STRING=$(az monitor app-insights component show --app myAppInsights --resource-group myResourceGroup --query connectionString --output tsv) # Create a Container Apps environment with the Dapr Application Insights connection string az containerapp env create --name myContainerAppEnv --resource-group myResourceGroup --logs-workspace-id $WORKSPACE_ID --logs-workspace-key $WORKSPACE_KEY --dapr-connection-string $CONNECTION_STRINGThe documentation also states that the parameter
--dapr-instrumentation-keyhas been deprecated. I suppose there is no way through CLI to configure the Instrumentation Key.Hope this helps! Please let us know if you have any additional questions or need further assistance.
-
Francisco Tineo Mateo 0 Reputation points
2024-11-14T02:41:03.28+00:00 Hi LeelaRajeshSayana,
We’ve done exactly like you posted many several times like mentioned in the post, both with azure cli and PowerShell and neither works. We can see the requests pass the parameters, but when the resource is created, the values show as null. We see this behavior for --dapr-connection-string (or -d) and for --logs-workspace-key.
We saw that dapr-instrumentation-key is deprecated in the documentation, but we’ve been passing it as well to see if it applies (no luck).
-
LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator
2024-11-18T17:25:59.18+00:00 Hi @Francisco Tineo Mateo For further assistance of this issue, please reach respond to the offline message.
-
Francisco Tineo Mateo 0 Reputation points
2024-11-18T17:31:14.7233333+00:00 We were informed that the APIs are setup to return null from the ARM and also show null on the portal as those values are considered secret. We recommended to update the az cli documentation to avoid confusion.
Sign in to comment
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more