Trouble Loading YAML as String Literal into other YAML.

[CJacobStucki]

I have this YAML file called omni-cert.yaml:

apiVersion: v1alpha1
kind: TrustedRootsConfig
name: custom-ca
certificates: |
	-----BEGIN CERTIFICATE-----
    MIIB/DCCAYKgAwIBAgIIT0QFSzf/fAkwCgYIKoZIzj0EAwMwIDEeMBwGA1UEAxMV
    bWluaWNhIHJvb3QgY2EgNGY0NDA1MCAXDTI1MDUxNTE1NDcxN1oYDzIxMjUwNTE1
	-----END CERTIFICATE-----

I have another YAML file called ProjectConfig.yaml:

omni:
	talosVersion: 1.11.3
	k8sVersion: 1.32.4
	omniCert: <omni_cert>

I'd like to inject the omni-cert.yaml file into the omniCert field of ProjectConfig.yaml

Command I tried:
yq '.omni.omniCert = load_str("/path/to/omni-cert.yaml")' /path/to/ProjectConfig.yaml

Result:

omni:
	talosVersion: 1.11.3
	k8sVersion: 1.32.4
	omniCert: "\e[36mapiVersion\e[0m:\e[32m v1alpha1\e[0m\r\n\e[32m\e[0m\e[36mkind\e[0m:\e[32m TrustedRootsConfig\e[0m\r\n\e[32m\e[0m\e[36mname\e[0m:\e[32m lmoc-ca\e[0m\r\n\e[32m\e[0m\e[36mcertificates\e[0m: |\r\n\e[32m  -----BEGIN CERTIFICATE-----\e[0m\r\n\e[32m  MIIB/DCCAYKgAwIBAgIIT0QFSzf/fAkwCgYIKoZIzj0EAwMwIDEeMBwGA1UEAxMV\e[0m\r\n\e[32m  bWluaWNhIHJvb3QgY2EgNGY0NDA1MCAXDTI1MDUxNTE1NDcxN1oYDzIxMjUwNTE1\e[0m\r\n\e[32m  -----END CERTIFICATE-----\e[0m\r\n\e[32m\e[0m\r\n

Expected (and desired) result:

omni:
	talosVersion: 1.11.3
	k8sVersion: 1.32.4
	omniCert: |-
		apiVersion: v1alpha1
		kind: TrustedRootsConfig
		name: custom-ca
		certificates: |
			-----BEGIN CERTIFICATE-----
    		MIIB/DCCAYKgAwIBAgIIT0QFSzf/fAkwCgYIKoZIzj0EAwMwIDEeMBwGA1UEAxMV
    		bWluaWNhIHJvb3QgY2EgNGY0NDA1MCAXDTI1MDUxNTE1NDcxN1oYDzIxMjUwNTE1
			-----END CERTIFICATE-----

Am I doing something wrong? Why does the loaded yaml have a bunch of strange characters added?

Using YQ version v4.49.2
Running commands from a ubi8-minimal:8.10 docker container with YQ installed on it.

[CJacobStucki]

I discovered what was happening for anyone else that runs into this.

I generated omni-cert.yaml with this command:
docker run --rm -it -v /opt/project:/opt/project -v /etc/certs:/etc/certs custom-container:0.0.1 yq '.certificates = str_load("/etc/certs/mycert.cer")' /opt/project/original-omni-cert.yaml > /opt/project/new-omni-cert.yaml

And then I was trying to generate the new project config a similar way:
docker run --rm -it -v /opt/project:/opt/project -v /etc/certs:/etc/certs custom-container:0.0.1 yq '.omni.omniCert = str_load("/opt/project/new-omni-cert.yaml")' /opt/project/original-ProjectConfig.yaml > /opt/project/new-ProjectConfig.yaml

After inspecting both of these files more closely, I found that something about trying to capture the output in the docker command in a new file (i.e. > new-file.yaml) was the issue, and was adding a bunch of garbage to the files for some reason. YQ still recognized them as valid yaml for some reason but other tools like dos2unix would see them as binary files.

Anyway, I instead tried to just edit the files with yq -i ... and that has given me the results I wanted.

So the command docker run --rm -it -v /opt/project:/opt/project -v /etc/certs:/etc/certs custom-container:0.0.1 yq -i '.omni.omniCert = str_load("/opt/project/omni-cert.yaml")' /opt/project/ProjectConfig.yaml > /opt/project/ProjectConfig.yaml

correctly generates the yaml I wanted:

omni:
	talosVersion: 1.11.3
	k8sVersion: 1.32.4
	omniCert: |
		apiVersion: v1alpha1
		kind: TrustedRootsConfig
		name: custom-ca
		certificates: |
			-----BEGIN CERTIFICATE-----
    		MIIB/DCCAYKgAwIBAgIIT0QFSzf/fAkwCgYIKoZIzj0EAwMwIDEeMBwGA1UEAxMV
    		bWluaWNhIHJvb3QgY2EgNGY0NDA1MCAXDTI1MDUxNTE1NDcxN1oYDzIxMjUwNTE1
			-----END CERTIFICATE-----