ansible/changelogs/fragments/67823-vault-unicode-string.yml
Matt Martz 9667f221a5
Make AnsibleVaultEncryptedUnicode work more like a string (#67823)
* Make AnsibleVaultEncryptedUnicode work more like a string. Fixes #24425

* Remove debugging

* Wrap some things

* Reduce diff

* data should always result in text

* add tests

* Don't just copy and paste, kids

* Add eq and ne back

* Go full UserString copy/paste

* Various version related fixes

* Remove trailing newline

* py2v3

* Add a test that can evaluate whether a variable is vault encrypted

* map was introduces in jinja2 2.7

* moar jinja

* type fix

Co-Authored-By: Sam Doran <sdoran@redhat.com>

* Remove duplicate __hash__

* Fix typo

* Add changelog fragment

* ci_complete

Co-authored-by: Sam Doran <sdoran@redhat.com>
2020-06-08 16:30:14 -05:00

6 lines
361 B
YAML

bugfixes:
- Vault - Make the single vaulted value ``AnsibleVaultEncryptedUnicode`` class
work more like a string by replicating the behavior of ``collections.UserString``
from Python. These changes don't allow it to be considered a string, but
most common python string actions will now work as expected.
(https://github.com/ansible/ansible/pull/67823)