Alex Vandiver 3aea67a8ed s3: Only use get_bucket to get to boto3 clients and resources. ...

boto3 has two different modalities of making API calls -- through
resources, and through clients.  Resources are a higher-level
abstraction, and thus more generally useful, but some APIs are only
accessible through clients.  It is possible to get to a client object
from a resource, but not vice versa.

Use `get_bucket(...).meta.client` when we need direct access to the
client object for more complex API calls; this lets all of the
configuration for how to access S3 to sit within `get_bucket`.  Client
objects are not bound to only one bucket, but we get to them based on
the bucket we will be interacting with, for clarity.

We removed the cached session object, as it serves no real purpose.

2024-01-05 11:12:18 -08:00

..

__init__.py

python: Consistently use from…import for urllib.parse.

2023-12-05 13:03:07 -08:00

base.py

models: Extract zerver.models.users.

2023-12-16 22:08:44 -08:00

local.py

mypy: Enable new error explicit-override.

2023-10-12 12:28:41 -07:00

s3.py

s3: Only use get_bucket to get to boto3 clients and resources.

2024-01-05 11:12:18 -08:00