Fix File Pair Processing of Modify and Deletion Overlap #881
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 #879 and similar patterns.
With this changed logic the module will check that whenever deployment jobs are constructed example:
baseTemplate
+parameterTemplate
it will check that neither file is being deleted in the same push to the module. If there in an overlap the file targeted for deletion will be skipped when constructing deployment jobs.Without this logic the module based on its current order of processing would unintentionally first re-process (deploy) the deleted file before proceeding with deletion.
This PR fixes/adds/changes/removes
Invoke-AzOpsPush.ps1
ConvertFrom-AzOpsBicepTemplate.ps1
Strings.psd1
Breaking Changes
N/A
Testing Evidence
Tests have been performed with the following combinations using both
.json, parameters.json, bicep, bicepparams
:baseTemplate
and removal ofparameterTemplate
parameterTemplate
and removal ofbaseTemplate
As part of this Pull Request I have
main
branch