Skip to content

feat(admin): add s3 as possible service destination

Michal Berky requested to merge mberky/STR-1495/s3_destination into main

Description

Adds s3 as available destination for propagation.

Accepts destination in the form of <endpoint-url>/<bucket-name> e.g. https://custom.endpoint.url/my-bucket. It must contain at least one slash dividing the two parts after protocol (which can be either https:// or http://). If there is more than the one slash, bucket-name will be the part after the last one and everything before that will be considered to be the endpoint url.

How to test

Deploy on devel or run locally (can also deploy perun!4504 (merged) on devel, but not necessary to test just the GUI part) and check that you can select s3 as service destination on facility and that invalid destinations are flagged as such and don't allow you to add them.

Author's checklist

  • I have followed the contribution guidelines
  • This MR has been tested or does not change functionality
  • I have added relevant merge request dependencies (if this MR has any)
  • I have added the correct labels
  • I have assigned reviewers (if any are relevant)
  • I have edited the documentation (if the changes require it) or I have noted the need for the change if I do not have access to the documentation
  • I have marked all introduced BREAKING CHANGES or necessary DEPLOYMENT NOTES in the commit message(s)

Reviewer's checklist

  • This MR has been tested or does not change functionality
  • This MR has correct commit message format

Related issues

Merge after perun!4504 (merged)

Closes STR-1495

Merge request reports