New version of the tier 3 template and new integration pattern #575
brooke-hamilton
announced in
Announcements
Replies: 1 comment
-
@brooke-hamilton Could you provide an example of how we would use a specific deploymentVariables file and send that into the mlzDeploymentVariables parameter? Hopefully in CLI and in PowerShell? I really appreciate it! I have tried Get-Content and ConvertFrom-Json but I am unable to get it to work. Thank you! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are modifying how we deploy add-ons to Mission Landing Zone, including the tier 3 (new workload) template. We are following the shared variable file pattern in which we generate a json file from the output of the Mission Landing Zone deployment, and that file is used by examples and add-ons to reference the state of the deployment.
Here's an example from the
newWorkload
README.mdThe
newWorkload.bicep
template has a reference to thedeploymentVariables.json
file generated above, and parameters have default values that come from the file. Here's a snippet from thenewWorkload
Bicep template:Beta Was this translation helpful? Give feedback.
All reactions