Feature/SK-1343 | Enable use of any S3 backend

[stefanhellander]

Description

Enables use of any S3 backend also when deployed via Studio.

[niklastheman]

Might be outside the scope of this pr but we could reflect about whether or not the Repository class is needed. Controller etc, could accept RepositoryBase as input which in turn then would be realized by MinioRepository or SaasRepositoty. There might be an explanation that for me is unclear, but it's an observation :)

[stefanhellander]

Might be outside the scope of this pr but we could reflect about whether or not the Repository class is needed. Controller etc, could accept RepositoryBase as input which in turn then would be realized by MinioRepository or SaasRepositoty. There might be an explanation that for me is unclear, but it's an observation :)

Absolutely, I think this should be cleaned up more. Probably should get rid of miniorepository.py as well and have one S3 class, but want to keep these changes as minimal as possible for now to ensure this also works with docker compose as well as old projects in the SaaS for now.

[niklastheman]

Might be outside the scope of this pr but we could reflect about whether or not the Repository class is needed. Controller etc, could accept RepositoryBase as input which in turn then would be realized by MinioRepository or SaasRepositoty. There might be an explanation that for me is unclear, but it's an observation :)

Absolutely, I think this should be cleaned up more. Probably should get rid of miniorepository.py as well and have one S3 class, but want to keep these changes as minimal as possible for now to ensure this also works with docker compose as well as old projects in the SaaS for now.

Sounds good!

[Wrede]

GJ!