yaml filters now use 'ansible yaml'

[bcoca]

Now they can process things like !unsafe and !vault

ISSUE TYPE

• Feature Pull Request

[nitzmahone]

I'm kinda torn about this overall...

In the process of determining which of our serialization formats would support round-tripping datatags, we leaned pretty heavily on the fact that from_yaml didn't support any custom tags today as justification for not defining a YAML tag scheme for datatags (which will be very difficult to do properly, given the limitations of YAML's tagging/type system). Even with this change, to_yaml still only preserves vault, not unsafe.

JSON is really our only "full fidelity round-trip capable" data interchange format today, and I'm thinking we should try to keep it that way. There are so many other gotchas around using Jinja to rewrite Ansible content that it might be good to just continue to let it fail early if someone's trying, rather than letting some stuff through. We'd also continue to fail on any doc that had other undefined tags, and since PyYAML doesn't provide anything out of the box to preserve that stuff, I think it's a lot easier to explain that those filters just don't support tagged data at all rather than defining a special subset that we'd likely face pressure to increase over time.

Doing multi-stream YAML support this way is also problematic, since it's now impossible to tell the difference between a doc with a root list and a list of docs. If we end up using multi-stream and need to support that with the filters, it probably needs to be a custom wrapper type that actually provides the context for each document.

[bcoca]

The multidoc support in the filters is preexisting, I just adapted it to be able to use Ansible's YAML as users were hitting an issue when exporting/generating the YAML and not being able to reimport/handle via the filters.

If we don't want to support having the filters understand/handle 'ansible YAML' then i can just turn this into a documentation PR.

[ansibot]

The test ansible-test sanity --test import --python 3.11 [explain] failed with 1 error:

lib/ansible/plugins/filter/core.py:36:0: traceback: ImportError: cannot import name 'from_yaml' from 'ansible.parsing.yaml' (/root/ansible/lib/ansible/parsing/yaml/__init__.py)

The test ansible-test sanity --test import --python 3.12 [explain] failed with 1 error:

lib/ansible/plugins/filter/core.py:36:0: traceback: ImportError: cannot import name 'from_yaml' from 'ansible.parsing.yaml' (/root/ansible/lib/ansible/parsing/yaml/__init__.py)

The test ansible-test sanity --test import --python 3.13 [explain] failed with 1 error:

lib/ansible/plugins/filter/core.py:36:0: traceback: ImportError: cannot import name 'from_yaml' from 'ansible.parsing.yaml' (/root/ansible/lib/ansible/parsing/yaml/__init__.py)

The test ansible-test sanity --test ansible-doc [explain] failed with the error:

Output on stderr from ansible-doc is considered an error.

Command "ansible-doc -l --json -t filter ansible.builtin" returned exit status 0.
>>> Standard Error
[WARNING]: Skipping file b'/root/ansible/lib/ansible/plugins/filter/core.py': "Failed to load b'/root/ansible/lib/ansible/plugins/filter/core.py' for ansible.builtin: cannot import name 'from_yaml' from 'ansible.parsing.yaml' (/root/ansible/lib/ansible/parsing/yaml/__init__.py)"
[WARNING]: Skipping plugin (/root/ansible/lib/ansible/plugins/filter/core.py), cannot load: cannot import name 'from_yaml' from 'ansible.parsing.yaml' (/root/ansible/lib/ansible/parsing/yaml/__init__.py)

The test ansible-test sanity --test pylint [explain] failed with 1 error:

lib/ansible/plugins/filter/core.py:35:0: unused-import: Unused yaml_load imported from ansible.module_utils.common.yaml

click here for bot help