Commits with a bicep file and ARM template parameter file generates 2 deployments

[StefanIvemo]

Describe the bug
If I commit a bicep file and a matching ARM template parameter file two deployments will be created by the push pipeline. One deployment for the bicep file and one for the parameter file.

Steps to reproduce

1. Create a bicep template, storage.bicep
2. Create an ARM template parameter file for the bicep template, storage.parameters.json
3. Open a Pull request. (This will generate a PR comment with the WhatIf result duplicated since two deployments are triggered)
4. Approve PR and merge to main branch
5. Two deployments will be created:
   • AzOps-storage
   • AzOps-storage.parameters

Screenshots

Screenshot shows deployment history for a commit with a bicep template named test1.bicep and a parameter file named test1.parameters.json.

[daltondhcp]

Great find! Right now, your parameters file (even for bicep deployments) will need to end with the extension .parameters.json similar to the examples in at https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/parameter-files.

[StefanIvemo]

Great find! Right now, your parameters file (even for bicep deployments) will need to end with the extension .parameters.json similar to the examples in at https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/parameter-files.

Of course, I made a typo in the issue. 😊