Sentry: Ancient boto3 & botocore versions

[mikeroll]

Any particular reason these are pinned? This gets in the a way a bit as I am developing an AWS plugin and the old boto3 api is lacking in some places.
Thanks!

[markstory]

We pin dependencies so that they don't slide into versions that contain breaking changes.

[mikeroll]

Yeah I'm not suggesting you unpin them completely, but perhaps it's possible to bump the pinned versions?

[markstory]

@mikeroll That's doable. Would you be willing to send a pukk request that bumps up to the version you need?

[max-rocket-internet]

Any update on this? Can we jump to a very recent version of boto so that newer IAM authentication mechanisms are supported?

[BYK]

@joshuarli @mattrobenolt any reason to not merge the attached PR?

[mattrobenolt]

My comment here still applies. https://github.com/getsentry/sentry/pull/13777#issuecomment-504564032

[BYK]

@mattrobenolt that's fine, we'll check for backwards compatibility. I'm guessing you have no other concerns then?

[mattrobenolt]

Nope, that's all.

[joshuarli]

@mattrobenolt Should we drop s3 support for filestore while we're at it? Not used in production + would take time to test and possibly port to newer boto3.

[mattrobenolt]

I think that'd be a bad idea. S3 is _very_ common. Nobody uses Google Storage except us, and we don't even use the backend here because of filestore.

[max-rocket-internet]

Should we drop s3 support

😅

[BYK]

Fixed via #22543.