Clean Up the Storage Services Configuration

[exalate-issue-sync]

Description

Clean up the storage services config

User Stories

• As an admin I need an understandable and logical way to configure and scale my storage services

Value

Clean and understandable configuration is key to a successful OSS project.

Implementation

• Create a subfolder in the storage service config pkg for every reva service (gateway, user storageprovider, home storageprovider, user dataproevider, home dataprovider, basic authprovider, bearer (openid) authprovider, publiclink authprovider ...).
• Use a separate config struct with only holds the needed config for every reva service
• Re Use shared config like Log Level and JWT secret
• Use the service names as a prefix (STORAGE, APPPROVIDER, USERPROVIDER...)

Acceptance Criteria

• The config of the storage services is cleaner and understandable
• We got rid of unnecessary duplications
• Generate config docs with the existing tooling are available (Extend if needed)

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] codre review happened
  [ ] CI is green
  [ ] critical code received unit tests by the developer
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues