Major update - need testers

[gabriel-samfira]

Hi folks!

A while ago I played around with the idea of using powershell classes and potentially adding an option to ConvertTo-Yaml to deserialize a yaml as a specific type. It was a really rough implementation, but I wanted to get a feeling of whether it would be useful or not to people.

I created a new implementation here:

#199

It combines a lot of the feedback we got over the years from the community. While it does not cover everything just yet, it does lean o the previous idea of deserializing to a powershell class or a PSCustomObject.

The changes are too broad co cover here as well, but I did add some info in the PR and you can find all the goodies that were added in the examples folder of the above PR.

A quick peek at what has been added:

• You can now deserialize to PSCustomObjects with support for most cases where you need to round-trip
• You can define your custom type-safe powershell classes to which you can deserialize your yaml. This offers the most flexibility, but is also the most verbose.
  • You can define custom yaml key mappings to class properties
  • You can define your own custom type converters if you need to
• Comments, flow style, quoting style and tags are preserved with both classes and PSCustomObjects

I need your help

While the old code is still there and should work as it always has, I need your help to test this in your environment to make sure that if we do release a new version of this, I won't break your workflows.

To the extent possible, please download the branch in the PR and test it in your workflow. If you feel brave enough, go through the examples folder and test out the new functionality as well. But at this point, I'll be happy to know if the large changes breaks existing setups.

As with anything new, don't use this in production (yet). Try it out in a test env.

Thanks in advance for the help!