The resource_config.yaml and comm_config.yaml are merged into one, and can be provided multiple times.

[mszostok]

Overview

The resource_config.yaml and comm_config.yaml are merged into one, and can be provided multiple times.
It’s up to the user how it will be split.

Acceptance Criteria

• All configuration settings can be defined in a single file.
  • The file name is not hard-coded. User can pick any name they want.
• Multiple files are merged together.
  • We should focus to merge the most top level properties. Complex, nested merging doesn't need to be supported.
• User is able to override given settings via environment variable, e.g. BOTKUBE_COMMUNICATIONS_SLACK_TOKEN

Reason

The resource_config.yaml and comm_config.yaml grow in a way that they don't hold the logic that the hard-coded file name says. Additionally, user needs to ensure that the file are named in that way, and don't have option to split them into multiple files. Currently, it needs to be one YAML files that get bigger and bigger.