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
We currently have a base exmaple/s set for deploying MLZ. It might benefit customers to see those examples in bash, PowerShell and using json via portal. These examples could use:
for example creating parameter object in PowerShell:
I'm temporarily removing this from a project backlog. Part of this work was done with #595 and I want to add scope for modifying the Bicep examples to be able to use any of these forms of setting parameters: PowerShell object, environment variables, parameters file, command line, and shared variable file pattern. That will mean removing the hard-coded references to a specific file path and providing each type of invocation with each example, but it will also allow adding the compiled ARM templates back into the source repo.
I will create a new backlog item that contains the scope above and close this one.
Benefit/Result/Outcome
We currently have a base exmaple/s set for deploying MLZ. It might benefit customers to see those examples in bash, PowerShell and using json via portal. These examples could use:
for example creating parameter object in PowerShell:
creating parameters via file:
Description
Ideally the examples will include a default parameter file they can customize, some default script commands they can copy and paste.
Acceptance Criteria
- with object
- with file
- command line directly
- with object
- with file
- command line directly
The text was updated successfully, but these errors were encountered: