Update Sentinel Deployment to include Bicep #512
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updated ./src/bicep/examples/sentinel to include Bicep modules to support the deployment of Sentinel onto an existing deployment of MLZ.
-sentinel.bicep: Makes use of a global variable file (MLZDeployment.Outputs). This has high re-usability simply because it can be referenced by any example that needs outputs from the initial MLZ deployment.
-deploySentinel: Is the Sentinel module that 'sentinel.bicep' uses to add Sentinel to existing Log Analytics workspace. This module can be called alone if there is no desire to use the variable file.
This should bring parity between Bicep and the current Terraform deployment for Sentinel
Issue reference
The issue this PR will close: #405
Checklist
Please make sure you've completed the relevant tasks for this PR out of the following list: