Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Converting inline defaults to defaults.yaml #57

Open
johnkeates opened this issue Aug 8, 2016 · 1 comment
Open

Converting inline defaults to defaults.yaml #57

johnkeates opened this issue Aug 8, 2016 · 1 comment

Comments

@johnkeates
Copy link
Contributor

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.

@daks
Copy link
Member

daks commented Nov 2, 2017

Hello,
I don't know if you made this job to convert to defaults.yaml+map.jinja, but I did it too :) (or part of it).
See PR GH-69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants