How to override yaml pipeline definitions with env vars?

[masci]

Is your feature request related to a problem? Please describe.
It is possible to override single fields in a pipeline yaml file by setting environment variables that follow a certain naming convention, e.g. for a pipeline like this:

components:
  - name: DocumentStore
    type: ElasticsearchDocumentStore
    params:
      host: localhost
      index: haystack_test

the value of an env var called DOCUMENTSTORE_PARAMS_INDEX would override haystack_test.

The API docs mention this feature in the context of the overwrite_with_env_variables function parameter but it's hard to find.

Describe the solution you'd like
Fine tuning a yaml definition through env var is instrumental when working with Containerized environments, and I'd like to see a dedicated section of the docs explaining this feature in detail, possibly with examples.

Describe alternatives you've considered
n/a

Additional context
Recently there was a discussion illustrating the problem.

[masci]

Converting to a discussion for reference, otherwise it's a "wontfix"