Skip to content

Json Scope Warnings should be treated as errors #338

@Gordonby

Description

@Gordonby

Describe the bug
During a Push pipeline, there has been a problem with the files included in the Diff.
Two warnings are present in the logs, then the pipeline competes successfully.
These warnings should be elevated to errors to prevent the pipeline from continuing.

WARNING: [10:49:32][New-AzOpsScope] Failed to: Creating a new scope from a path | Conversion from JSON failed with error: After parsing a value an unexpected character was encountered: ". Path 'parameters.nonCompliantMessage', line 20, position 8.

WARNING: [10:49:32][New-AzOpsDeployment] Failed to resolve the scope for template /home/vsts/work/1/s/azops-canary/canary (canary)/SampleAssignment.json and parameters /home/vsts/work/1/s/azops--canary/canary (canary)/SampleAssignment.parameters.json | Conversion from JSON failed with error: After parsing a value an unexpected character was encountered: ". Path 'parameters.nonCompliantMessage', line 20, position 8.

Screenshots
image

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions