<@U06A03HV1> There's a... well it isn't a bug, but...
# development
b
@witty-crayon-22786 There's a... well it isn't a bug, but isn't not a bug in 2.16.x. Using the new
s3
URL Handler, I'm seeing:
Copy code
File "/home/ubuntu/.cache/nce/1239dc7f2c4e6bb57836aa10d4b93b4a7bd7016bedcb8ca326ef6b803855e362/bindings/venvs/2.16.0rc2/lib/python3.9/site-packages/pants/backend/url_handlers/s3/register.py", line 85, in download_from_s3

    signer.add_auth(http_request)

  File "/home/ubuntu/.cache/pants/named_caches/pex_root/venvs/s/1968668f/venv/lib/python3.9/site-packages/botocore/auth.py", line 833, in add_auth

    signature = self.get_signature(

  File "/home/ubuntu/.cache/pants/named_caches/pex_root/venvs/s/1968668f/venv/lib/python3.9/site-packages/botocore/auth.py", line 819, in get_signature

    del headers['x-amz-security-token']

KeyError: 'x-amz-security-token'
Using
botocore-a-la-carte
as a plugin. I upstreamed the fix and is in PR: https://github.com/boto/botocore/pull/2948 who the hell knows when that goes in. ...I have no idea why this didn't fire earlier, or why the tests pass. The code in question is 9 years old. So... might wanna 🍒 a Pants workaround 😕
I also am only seeing this in CI, and not locally? I'm very confused 🫠
I understand now. Token-based auth vs access/secret key creds. 🫠
💩 1