yaml: >=2.2.2

[rak-phillip]

No description provided.

[yonasberhe23]

dependency bump touches Harvester, we should probably do smoke test to ensure nothing is broken there. Moving to To Test

[izaac]

@rak-phillip what would be the result in case it's broken on Harvester? It's a one off broken or working scenario? Or does it involve a more detailed validation.

If the former I think we can move this one to done, as there are other 2.10 Harvester issues pending validation already.

[rak-phillip]

@izaac see this comment in the associated PR for more details

#12103 (review)

the YAML dependency is used to handle the User Data field as a yaml.

If it is broken for any reason, we can anticipate that one of the following might occur

• data does not render for this field
• data does render, but is not properly parsed as YAML
• uncaught errors are printed to the console

[izaac]

Validated on Rancher version: v2.10.0-alpha11
UI version: v2.10.0-alpha6
Harvester plugin version: 1.0.0
Harvester clusters versions: 1.4-head and 1.3.2 - (1.4 target is Rancher 2.10).

I was able to navigate without issues between the two imported Harvester clusters in the Virtualization Management.
I've provisioned a Virtual Machine too on each cluster and the User Data field were rendered properly in the UI showing the YAML.