-
Notifications
You must be signed in to change notification settings - Fork 59
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
token
must be of type str or bytes, not <class 'ansible.utils.unsafe_proxy.AnsibleUnsafeText'>
#289
Comments
It appears that this is due to a change in This probably means the token returned as always being marked as unsafe anyway, or perhaps that happened after the token changes in 1.10, but either way, It seems they are reluctant to change this behavior back despite it being breaking; even if gets reverted it will probably happen again in another release. Will have to see what we can do on our side. |
The workaround I've been working on is to internally ensure that tokens are always strings when we pass them to the client. Hope to have a PR up for this soon. |
token
must be of type str or bytes, not <class 'ansible.utils.unsafe_proxy.AnsibleUnsafeText'>
I came across the same issue. The latest version I can install with pip which does not run into this bug is this:
|
SUMMARY
Seeing some failures in daily CI today in devel:
It looks like something has changed causing the result to be considered "unsafe" from various lookups.
ISSUE TYPE
COMPONENT NAME
auth_token
lookup_hashi_vault
lookup_vault_kv1_get
lookup_vault_kv2_get
lookup_vault_login
lookup_vault_read
lookup_vault_token_create
lookup_vault_write
ANSIBLE VERSION
devel
COLLECTION VERSION
current
The text was updated successfully, but these errors were encountered: