Adding support for .bicepparam and always export WhatIf results #820
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.
Overview/Summary
This PR fixes #816 by adding AzOps support for
.bicepparam
parameter files.This PR fixes #817 by ensuring that WhatIf results are exported to
OUTPUT.json
at everyvalidate
run.This PR contains dependency bumps:
Az.Accounts 2.12.5
Az.Billing 2.0.3
Az.Resources 6.9.1
PSFramework 1.8.291
This PR fixes/adds/changes/removes
Invoke-AzOpsPush.ps1
ConvertFrom-AzOpsBicepTemplate.ps1
Set-AzOpsWhatIfOutput.ps1
Strings.psd1
Repository.Tests.ps1
bicepparamtest.bicep
bicepparamtest.bicepparam
policywithuam.bicep
policywithuam.bicepparam
Breaking Changes
N/A
Testing Evidence
This PR adds one new automated test of

.bicepparam
and changes one exsiting test to also cover.bicepparam
scenarios.In addition to that manual tests have been performed to validate WhatIf
OUTPUT.json
content.As part of this Pull Request I have
main
branch