[AzureResourceManagerTemplateDeployment] - Fix for bicep param file with multiple extensions #19581
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.
Task name: AzureResourceManagerTemplateDeployment
Description: Fixes
.bicepparam
file support to work when bicep param file has multiple file extensions likemain.ENVNAME.bicepparm
it results in amain.parameters.json
file as expected.This new code will now properly detect when more than one file extension is applied and properly remove all file extensions before replacing with
.parameters.json
.Documentation changes required: No
Added unit tests: Yes, unit test was added to cover this use case
Attached related issue: Yes, Comment on previous PR with this issue
Checklist:
Link to pipeline run with new version of task code
Passing unit tests: