Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set node position for vault encrypted objects #60631

Closed
wants to merge 1 commit into from

Conversation

@commx
Copy link

commented Aug 15, 2019

SUMMARY

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.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

Core YAML Parsing

ADDITIONAL INFORMATION

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.

@commx

This comment has been minimized.

Copy link
Author

commented Aug 15, 2019

ready_for_review

@sivel sivel added P3 and removed needs_triage labels Aug 15, 2019

@ansibot ansibot added the stale_ci label Aug 23, 2019

@commx commx closed this Aug 28, 2019

@commx commx reopened this Aug 28, 2019

@ansibot ansibot removed the stale_ci label Aug 28, 2019

@commx commx closed this Aug 30, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.