Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
set node position for vault encrypted objects #60631
The change sets the node position for vault encrypted YAML objects, just like it does for other objects types like strings, mappings and sequences. This allows third-party scripts to retrieve the source position of a specific variable.
Core YAML Parsing
I recently wrote a script that utilises Ansible's Variable Manager to query specific variables out of a set of inventory variable files. For informational reasons, it is supposed to gather the source file and line number of a variable. This works just fine for strings, sequences and mappings - but won't work for vault encrypted unicode objects, because it doesn't set the ansible_pos property like it does for the other type objects.
The change will align the same standard for vault encrypted unicode objects as it does for strings, sequences, etc.