Skip to content

way to manage haproxy package repository #70

@daks

Description

@daks

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.

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