Bicep version
0.27.1 (4b41cb6)
Describe the bug
bicep build-params with a bicepparam file as input behaves differently depending on what output you specify, --stdout vs. --outdir.
--stdout returns a full template with the .bicep file the .bicepparam points to.
--outdir only creates a parameters.json file.
I can't find info saying this difference is intended:
To Reproduce
Bicep v0.27.1 (4b41cb6), a params.bicepparam poiting to a main.bicep. Watch difference of output when:
az bicep build-params --file ".\params.bicepparam" --stdout
# or
bicep build-params ".\params.bicepparam" --stdout
# VS
az bicep build-params --file ".\params.bicepparam" --outdir ".\"
# or
bicep build-params ".\params.bicepparam" --outdir ".\"
Additional context
Add any other context about the problem here.
Bicep version
0.27.1 (4b41cb6)
Describe the bug
bicep build-paramswith a bicepparam file as input behaves differently depending on what output you specify,--stdoutvs.--outdir.--stdoutreturns a full template with the .bicep file the .bicepparam points to.--outdironly creates a parameters.json file.I can't find info saying this difference is intended:
To Reproduce
Bicep v0.27.1 (4b41cb6), a
params.bicepparampoiting to amain.bicep. Watch difference of output when:Additional context
Add any other context about the problem here.