`error converting YAML to JSON` when using databricks bundle

[ericfeunekes]

I created a bundle.yml file to test deployment of a single pipeline. When I run either databricks bundle validate or deploy I get the message Error: error converting YAML to JSON: yaml: found character that cannot start any token.

I've double checked that all tabs are converted to spaces, used a yaml linter to validate the file, and successfully loaded the file in python using PyYAML. If there is an error in the file, it would good to get a pointer to the issue.

cli version: v0.200.1
os: Mac OS 13.4 (M1)

[pietern]

Thanks for reporting the issue. Do you have other yaml files in the same directory by any chance?

If not specified explicitly, the configuration defaults to loading *.yml and */*.yml in the bundle root.

Load errors don't include the file name today but will in the next patch release, to make that more clear.

[ericfeunekes]

Thanks for reporting the issue. Do you have other yaml files in the same directory by any chance?

No other yaml files in the same directory no. And when I remove the bundle.yml it gives an error that it can't find a bundle file. So I think it's finding the correct file.

If not specified explicitly, the configuration defaults to loading *.yml and /.yml in the bundle root.

I don't see any way to specify the bundle file explicitly. Regardless, when I run databricks bundle validate bundle.yml it gives me the same error.

I have yaml linting turned on and it's not raising any errors. I even reduced the file to just 7 lines and am getting the same error. I attached the bundle file I'm using below to see if the error can be reproduced (github doesn't support yaml, so I had to call it a txt file. You can change the suffix to yml and get the file I'm using).

bundle copy.txt

[pietern]

When I try the same with the file you provided it works as expected (same CLI version and OS).

Could you send an email to dabs-preview@databricks.com, so we can setup time to meet and repro?

I'd like to get to the bottom of this.

[ericfeunekes]

Just adding a comment for others who find this. Currently the bundle commands glob **/*.yml so if you have other yml files in a subdirectory they could cause this.

The temporary solution is to include a fake file name in your bundle file:

include:
  - fake.yml

This stops the subdirectory search.

[andrewnester]

Has been resolved in this PR #602