Fix Duplicate conflicting deployments with DeployAllMultipleTemplateParameterFiles #887
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 changes two key pieces to fix #886 and avoid incorrect recursive parameter discovery.
$deploymentName
is derived at run-time. Ensuring that if the deployment job que contains overlapping deployments, we only process it once when they have matching deployment name and files.This PR fixes/adds/changes/removes
Invoke-AzOpsPush.ps1
Repository.Tests.ps1
decoy.westeurope.bicep
decoy.westeurope.x123.parameters.json
deployallrt.westeurope.bicep
deployallrt.westeurope.x123.parameters.json
deployallrt.westeurope.xabc.bicepparam
deployallrt2.westeurope.bicep
Breaking Changes
Testing Evidence
The logic has been tested according to the issue and an automated test has been added.
As part of this Pull Request I have
main
branch