Skip to content

Allow aliasing a service so that it's available under more than one name #4

@mwiencek

Description

@mwiencek

We currently make use of hard-coded service names in consul template files, e.g. {{if service "postgres-master"}}, {{if service "pgbouncer-slave"}}, etc.

Since these map to specific nodes and are a pain to update when we perform a switchover, an haproxy service will be added that detects the current primary and standbys. It will expose the following services: haproxy-postgres-primary, haproxy-postgres-standby, haproxy-postgres-any.

It would be nice if we could keep the new service naming convention while also continuing to allow access to a postgres-master service (which would map to haproxy-postgres-primary). This way existing consul template files will continue to work, and can be updated incrementally without any downtime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions