feat: use env variable in yaml config files

[micbar]

Description

We added the ability to use environment variables in yaml config files. This allows to use environment variables in the config files of the ocis services which will be replaced by the actual value of the environment variable at runtime.

Example:

web:
  http:
    addr: ${SOME_HTTP_ADDR}

This makes it possible to use the same config file for different environments without the need to change the config file itself. This is especially useful when using docker-compose to run the ocis services. It is a common pattern to create an .env file which contains the environment variables for the docker-compose file. Now you can use the same .env file to configure the ocis services.

Related Issue

• Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

• test environment:
• test case 1:
• test case 2:
• ...

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[micbar]

@mmattel @dragonchaser @kobergj

I suggest to hold this and not commit it to the 5.0.0 release.

[butonic]

@kobergj @dragonchaser I think we should merge this for OCIS v5. Existing yaml files will not contain any ${ENV_VAR} replacements or they would likely be failing anyways. If an admin wants to use them he has to check the env vars anyway. So this should go in sooner rather than later.

[mmattel]

CI complains about a changlog issue

[sonarcloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud