-
Notifications
You must be signed in to change notification settings - Fork 762
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
Can the bicep cli also have an option to build the corresponding json parameters file #2626
Comments
We do plan to do this, but in the meantime I'd recommend the Bicep powershell module from @StefanIvemo. It already has the ability to generate a parameters file, but atm it requires building the bicep code as well. Since PS and CLI natively read Going to close this and track with #512 in the meantime. |
Just released version # Generate a parameter file with all parameters from the bicep file
New-BicepParameterFile -Path .\main.bicep -Parameters All
or
# Generate a parameter file with required parameters from the bicep file only
New-BicepParameterFile -Path .\main.bicep -Parameters Required This will generate an ARM template parameter file that can be used for deployment: az deployment sub create -f main.bicep -p main.parameters.json -l eastus -c |
Do we have the same using az cli? |
Is your feature request related to a problem? Please describe.
Right now the bicep cli can be used the build json templates from the bicep template. Can it be enhanced to build the parameters file for a template
Describe the solution you'd like
A clear and concise description of what you want to happen.
The text was updated successfully, but these errors were encountered: