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
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
Observed behaviour:
I'm deploying ACI container groups with ARM template. The attributes Microsoft.ContainerInstance/containerGroups/diagnostics.logAnalytics.workspaceId and Microsoft.ContainerInstance/containerGroups/diagnostics.logAnalytics.workspaceKey to not appear to be validated upon deployment. I can enter any workspaceId, e.g. "thisisnotavalidID", and I can enter the wrong workspaceKey for a valid workspaceId, but the container group is still deployed, and log collection by Log Analytics Workspace fails silently.
Expected behaviour:
If I try to deploy a container group with invalid Log Analytics Workspace credentials, the deployment should fail. Any combination of workspaceId and workspaceKey which do not correspond to an existing workspace where workspaceKey is a valid key, should fail.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Observed behaviour:
I'm deploying ACI container groups with ARM template. The attributes
Microsoft.ContainerInstance/containerGroups/diagnostics.logAnalytics.workspaceId
andMicrosoft.ContainerInstance/containerGroups/diagnostics.logAnalytics.workspaceKey
to not appear to be validated upon deployment. I can enter anyworkspaceId
, e.g. "thisisnotavalidID", and I can enter the wrongworkspaceKey
for a validworkspaceId
, but the container group is still deployed, and log collection by Log Analytics Workspace fails silently.Expected behaviour:
If I try to deploy a container group with invalid Log Analytics Workspace credentials, the deployment should fail. Any combination of
workspaceId
andworkspaceKey
which do not correspond to an existing workspace whereworkspaceKey
is a valid key, should fail.The text was updated successfully, but these errors were encountered: