Closed briantist closed 2 years ago
It appears that this is due to a change in requests
unfortunately:
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, requests
was turning them back into regular strings.
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.
I came across the same issue. The latest version I can install with pip which does not run into this bug is this:
pip install ansible==6.7.0
@fansari this should have been fixed in #291 in collection version 3.2.0
. When you run ansible-galaxy collection list
what version of this collection do you see?
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