Open bethac07 opened 2 years ago
I think we don't actually need to do anything?
My understanding of the botocore issue is that they are deprecating accepting endpoints given as {region}.{service}.{dnsSuffix}
and will only accept {service}.{region}.{dnsSuffix}
.
I don't think this applies to us as we are not explicitly naming the endpoint nor are we explicitly allowing domains anywhere. Instead, we use boto3 client sqs.list_queues()
and boto3 resource sqs.get_queue_by_name()
.
Usually a future warning will only get popped if you're actually passing it the format that's about to be deprecated, so we probably want to check what we're currently getting - but yes, you would HOPE that in general if boto3 is handling it all, it will do so correctly. Might just mean a minimum version of boto3 and/or botocore.
Where/when did the warning print for you?
I've got a run going now. I made my own DCP docker FROM cellprofiler/cellprofiler:4.2.4
. I'm not noticing this warning anywhere but the queue I made defaulted to having Server-Side Encryption which is new...
A couple of different machines that I was launching DCP from. I can grab the pip freeze
's next time I'm on. Since it's on the machine you launch from, rather than the Docker, the exact docker version shouldn't matter.
Ah, right! The machine I just used has boto3==1.16.49
botocore==1.19.49
.
If I update to boto3==1.24.77
and botocore==1.27.77
I do get the warning.
My queue is also still defaulting to SSE though it looks like my machines are pulling jobs from the queue without a problem so changing back to our old default of Encryption Disabled may not be necessary...