Skip to content

Converting inline defaults to defaults.yaml #57

@johnkeates

Description

@johnkeates

This is more of a notification than a bug; I'm converting some of the stuff that's gotten to be inline defaults to the slightly more standard (and definitely more flexible) defaults.yaml + map.jinja combination. This came out of my need to install different haproxy versions, i.e. 1.6 via backports and 1.5 on LTS versions of operating systems. I'm also adding initial provisions for an OS Map so you can have different defaults per OS with automated filtering built in.

While this won't break the formula, it might make people with special configs unhappy as some of their defaults they set via the pillar might now be located in a different spot.

I'll try to keep any variable names as they are so most people won't need to do things about their current configs.

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