-
Notifications
You must be signed in to change notification settings - Fork 140
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
Exposed 'deploySentinel' as an available parameter #515
Conversation
src/bicep/mlz.bicep
Outdated
@@ -487,6 +487,8 @@ param logAnalyticsWorkspaceLocation string = operationsLocation | |||
param logAnalyticsWorkspaceCappingDailyQuotaGb int = -1 | |||
param logAnalyticsWorkspaceRetentionInDays int = 30 | |||
param logAnalyticsWorkspaceSkuName string = 'PerGB2018' | |||
@description('When set to "True", enables Microsoft Sentinel within the MLZ Log Analytics workspace.') | |||
param enableSentinel bool = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's name this deploySentinel
for consistency -- the rest of the on/off switches are deploy{X}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes sir, just updated the branch as requested. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ExchMaster 👍
Description
The module, "./src/bicep/modules/logAnalyticsWorkspace.bicep" parameter was set to 'False' and not exposed as param within mlz.bicep. This PR allows for setting this value to true as part of the base deployment of MLZ. This PR does not change the default behavior which is "deploySentinel = false".
Successfully tested the new param by setting it to 'true' and deploying a new MLZ instance in both Azure Commercial and Azure Government. Both deployments worked flawlessly and as expected with Azure Sentinel deployed successfully and collecting metrics appropriately.
Issue reference
The issue this PR will close: #405, this might also be seen as an update along with #468
Checklist
Please make sure you've completed the relevant tasks for this PR out of the following list: