Skip to content

Environment variable configuration precedence over file #95

@foudfou

Description

@foudfou

Hi,

The comments (and possibly some documentation somewhere) states that env vars take precedence over the config file.

But this is not true in the current implementation which looks at the config file first.

Besides, if the config file is not accessible for some reason, loadINI() fails without considering the env variables. For example: ovh: new client: cannot load configuration: open ./ovh.conf: permission denied

I think the logic that I would expect is: either of the following in order:

  1. env vars
  2. local config file (./)
  3. home config file (~/)
  4. general config file (/etc/)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions