attachment_s3: multi-tenancy use db name in bucket

Adds the possibility to insert `{db}` placeholder in the bucket name
that will be replaced by the database name to form a unique bucket
name per database.
This commit is contained in:
Yannick Vaucher committed 2021-05-27 18:17:51 +02:00
1 parent 1bd88f1e72
commit 6aeebfc455
2 files changed
+15 -1

No files matched your search

+13 -1
View File
@@ -18,7 +18,7 @@ Configure accesses with environment variables:
* ``AWS_REGION`` (required if using AWS services)
* ``AWS_ACCESS_KEY_ID``
* ``AWS_SECRET_ACCESS_KEY``
* ``AWS_BUCKETNAME``
* ``AWS_BUCKETNAME`` (optional {db} placeholder)
Read-only mode:
@@ -38,6 +38,18 @@ The System Parameter ``ir_attachment.storage.force.database`` can be customized
force storage of files in the database. See the documentation of the module
``base_attachment_object_storage``.
Multi-tenancy
-------------
Use the `{db}` placeholder to handle multi-tenancy.
On instances that hold multiple databases, it's preferable to have one bucket per database.
To handle this, you can insert the `{db}` placeholder in your bucket name variable ``AWS_BUCKETNAME``.
It will be replaced by the database name.
This will give you a unique bucketname per database.
Limitations
-----------
+2
View File
@@ -56,6 +56,8 @@ class IrAttachment(models.Model):
access_key = os.environ.get('AWS_ACCESS_KEY_ID')
secret_key = os.environ.get('AWS_SECRET_ACCESS_KEY')
bucket_name = name or os.environ.get('AWS_BUCKETNAME')
# replaces {db} by the database name to handle multi-tenancy
bucket_name.format(db=self.env.cr.dbname)
params = {
'aws_access_key_id': access_key,
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.