You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying a template alongside a parameter.json file the Azure DevOps log outputs a warning for the parameter.json.
WARNING: [13:37:00][AzOpsScope] Unable to determine type from Template or Template Parameter file: /home/vsts/work/1/s/root/root <...>/templateName.parameters.json
As this parameter file isn't even supposed to be deployed this warning clutters the output and gives bad feedback.
Suggestions
Either make this an opt in and only show this message when high verbosity or similar is set, or
Change this to a informational message or
Do not parse/include .parameters.json files at all in the list of files to process as they most likely aren't ment to be deployed..
Steps to reproduce
Deploy a resource.bicep with a resource.parameters.json
check the Azure DevOps output
Screenshots
The text was updated successfully, but these errors were encountered:
Regarding alternative 3 there is a scenario where only the parameters file is present in git - see discussion in #677.
Somewhat related... if you deploy a resource group using an ARM template with a params file the params file is deleted by the next pull and the subsequent Validate/Push will fail.
daltondhcp
changed the title
Bug Report
Undesired warning in pipeline output for parameter files during deployment/validate
Nov 30, 2022
Describe the bug
Related to #504 (?)
When deploying a template alongside a parameter.json file the Azure DevOps log outputs a warning for the parameter.json.
As this parameter file isn't even supposed to be deployed this warning clutters the output and gives bad feedback.
Suggestions
Either make this an opt in and only show this message when high verbosity or similar is set,
or
Change this to a informational message
or
Do not parse/include .parameters.json files at all in the list of files to process as they most likely aren't ment to be deployed..
Steps to reproduce
Screenshots
The text was updated successfully, but these errors were encountered: