# Facilitate ansible-vaulting of variables from within text editors

**URL:** <https://forum.ansible.com/t/facilitate-ansible-vaulting-of-variables-from-within-text-editors/2527>\
**Category:** Project Discussions\
**Tags:** yaml, ansible-vault\
**Created:** [November 22, 2023, 10:11pm UTC](https://forum.ansible.com/t/facilitate-ansible-vaulting-of-variables-from-within-text-editors/2527 "2023-11-22T22:11:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [November 22, 2023, 10:11pm UTC](https://forum.ansible.com/t/facilitate-ansible-vaulting-of-variables-from-within-text-editors/2527/1 "2023-11-22T22:11:56Z")

</div>

Continuing the discussion from [Parsing and vaulting yaml the Ansible way with ruamel.yaml](http://forum.ansible.com/t/parsing-and-vaulting-yaml-the-ansible-way-with-ruamel-yaml/2433):

This code now has a [github repo](https://github.com/utoddl/av-filter) to make collaboration easier. Your participation is welcome.

Here’s an interesting suggestion: When decrypting a previously vaulted value, rather than returning the plain scalar value, stick a YAML “`!unvaulted`” tag on it. This would enable pre-commit hooks to detect and prevent inadvertent attempts to commit secrets in plain text. The user could easily remove the tag or update and/or re-vault the data. If this is implemented, we should make it possible to “revault” such `!unvaulted` tagged data without having to remove the tag.

Fun project, fun times!