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

(MODULES-2704) Consistent use of ::haproxy::config_file #201

Merged
merged 1 commit into from
Oct 16, 2015

Conversation

traylenator
Copy link

Previously

haproxy{'whatever':
  config_file => /tmp/haproxy.cfg
}
haproxy::peers{'mypeers':}
haproxy::peer{'peerA':
   peers_name    => 'mypeers',
   port                 => 5000,
   ipaddresses    => ['1.2.3.4','5.6.7.8],
   server_names => ['a.example.org','b.example.org']
}

would fail since haproxy:peer and peers were
hardcoded to use /etc/haproxy/haproxy.cfg

haproxy::config_file is now respected consistently
throughout the module.

https://tickets.puppetlabs.com/browse/MODULES-2704

Previously

```puppet
haproxy{'whatever':
  config_file => /tmp/haproxy.cfg
}
haproxy::peers{'mypeers':}
haproxy::peer{'peerA':
   peers_name    => 'mypeers',
   port                 => 5000,
   ipaddresses    => ['1.2.3.4','5.6.7.8],
   server_names => ['a.example.org','b.example.org']
}
```
would fail since haproxy:peer and peers were
hardcoded to use */etc/haproxy/haproxy.cfg*

haproxy::config_file is now respected consistently
throughout the module.

https://tickets.puppetlabs.com/browse/MODULES-2704
mentat added a commit that referenced this pull request Oct 16, 2015
(MODULES-2704) Consistent use of ::haproxy::config_file
@mentat mentat merged commit 1c218e6 into puppetlabs:master Oct 16, 2015
@mentat
Copy link

mentat commented Oct 16, 2015

Thanks for this. Good catch.

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

Successfully merging this pull request may close these issues.

3 participants