Skip to content

Better configuration validation #111

Description

@mcpherrinm

Right now, we allow some conflicting configuration values. Like you can configure a unix socket and a TLS certificate and key, which will be ignored. Or if you configure just a certificate, you'll get an error loading the key.

We should be more explicit about what options are required, and not allow "useless" flags.

If a unix:// url is provided, we could require an empty host and nonempty path

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