Allow customization of S3 settings on a per-tenant basis

Description

Add support to the deployments service (both OS and enterprise) to:

  • get and set the AWS settings (region, bucket, uri, key, secret, token)

  • use the settings above instead of the ones from the configuration file

  • if no setting is found in the database, use the configuration from the config file

Acceptance criterias:

  • API documentations to get and set the AWS settings above

  • API implementation to get and set the AWS settings above

  • Unit and (if needed acceptance) tests

  • Update to the service to use the settings above if present

Affects versions

None

Environment

None

Checklist

Activity

Show:

Alex MiliukovMay 5, 2021 at 1:42 PM

the ticket is done already. How do you think should we add it to the sprint or just close it in the backlog?

Alex MiliukovApril 30, 2021 at 11:08 AM

Alex MiliukovApril 30, 2021 at 5:53 AM

Alex MiliukovApril 30, 2021 at 5:53 AM

As agreed on the current implementation stage we'll be doing one extra read request to MongoDB, which will increase traffic and might increase response times, but it should be acceptable at current stage. More advanced implementation significantly complicates things, which is not preferred at the moment.

Fixed

Details

Assignee

Reporter

Story Points

Priority

Days in progress

0

Backlog

yes

Zendesk Support

Checklist

Created April 15, 2021 at 8:39 AM
Updated May 5, 2021 at 2:06 PM
Resolved May 5, 2021 at 2:06 PM