YAML migration for Azure-Kusto query

Question

I'm trying to trigger a gate check in YAML, this is what I have so far, with the sensitive bits removed. What is wrong with this snippet? I'm getting the following error -

Encountered error(s) while parsing pipeline YAML: /pipelines/Official/xl/officepy/mobr/output/officepysvc-release-pipeline-sdp-input_yaml.yml: (Line: 107, Col: 13, Idx: 3431) - (Line: 107, Col: 13, Idx: 3431): Mapping values are not allowed in this context.

- job: CustomJob
	pool:
	type: release
	steps:
	- task: Azure-Kusto.PublishToADX.PublishToADX.PublishToADX@4
inputs:
serviceConnection: 'svc connection name goes here'
targetType: 'inline'
script: |
let pst = datetime_utc_to_local(now(), 'US/Pacific');
| where not(isDeploymentAllowed)
|project ringType, startHour, endHour, businessDays, withinBusinessHours, isDeploymentAllowed, currentDayOfWeek                       waitForOperation: true
kustoUrls: 'URL goes here'
continueOnError: false

Answer 1

@Abhay Punjabi

Welcome to the Microsoft Q&A and thank you for posting your questions here

It looks like there are a few indentation issues in your YAML snippet. YAML is very sensitive to indentation, and it seems that the inputs block is not properly indented under the task. Here’s a corrected version:

- job: CustomJob
  pool:
    type: release
  steps:
    - task: Azure-Kusto.PublishToADX.PublishToADX.PublishToADX@4
      inputs:
        serviceConnection: 'svc connection name goes here'
        targetType: 'inline'
        script: |
          let pst = datetime_utc_to_local(now(), 'US/Pacific');
          | where not(isDeploymentAllowed)
          | project ringType, startHour, endHour, businessDays, withinBusinessHours, isDeploymentAllowed, currentDayOfWeek
        waitForOperation: true
        kustoUrls: 'URL goes here'
        continueOnError: false

Make sure that each level of indentation is consistent. In this case, inputs should be indented under task, and the properties under inputs should be indented further. This should resolve the parsing error you’re encountering.

Hope this helps. Do let us know if you any further queries.