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

way to manage haproxy package repository #70

Open
daks opened this issue Nov 2, 2017 · 1 comment
Open

way to manage haproxy package repository #70

daks opened this issue Nov 2, 2017 · 1 comment

Comments

@daks
Copy link
Member

daks commented Nov 2, 2017

Hello,

at the moment, there is no way in the formula to specify from which repository Haproxy package must be installed. The only way is to extend the formula.

I think this is a standard need which can easily be added. I thought about two ways to do it:

  • first one, simply adding a 'haproxy:fromrepo' pillar and in install.sls check if it exists and use it if it does
  • second one, depending of the merge of Switching to map.jinja to define platform specific values #69, to add a default value in map.jinja and use it. Then allow overriding it with 'haproxy:lookup:fromrepo'

I prefer the second one, which I found prettier and cleanier, but I may not be totally partial :)

I would like to know what people think about it.

@daks
Copy link
Member Author

daks commented Nov 3, 2017

I'm not sure anymore what is the best solution. I checked some other formulas and few (if not none) implement this functionality in map.jinja, I don't know if they implement it another way.

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

1 participant