-
Notifications
You must be signed in to change notification settings - Fork 26
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
cMMAgentOpsInsights not changing workspace ID and KEY #16
Comments
Thank you for reporting this issue. This module is moving to OMSDsc. I will push the Log Analytics resources end of next week. Please use them. |
I released an preview version of the OMSDsc module. It is not on gallery yet but resolves this issue. Please feel free to test this. I ma closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm looking at your DSC resource to use it within Azure DSC, but your custom DSC resource doesn't seem to change the workspace ID and Key.
Configuration MMAgentConfiguration
{
$OPSINSIGHTS_WS_ID = Get-AutomationVariable -Name "LA_WA_ID_02"
$OPSINSIGHTS_WS_KEY = Get-AutomationVariable -Name "LA_WA_KEY_02"
Node OMSnode {
cMMAgentOpInsights MMAgentOpInsights {
WorkspaceID = $OPSINSIGHTS_WS_ID
WorkspaceKey = $OPSINSIGHTS_WS_KEY
Ensure = 'Present'
}
}
}
The text was updated successfully, but these errors were encountered: