Including `haproxy::app_lb` in run list doesn't write proper haproxy.cfg

[sous-chefs]

Including `haproxy::app_lb` in run list doesn't write proper haproxy.cfg

[alxndrmlr]

@ianrossi were you able to resolve this. I'm running into this as well.

[ianrossi]

@alxndrmlr I worked around this by using the develop branch. I'm using librarian-chef for cookbook dependency management, so I put the following in my Cheffile:

cookbook 'haproxy', :git => '[email protected]:hw-cookbooks/haproxy.git', :ref => 'develop'

Then, I install all cookbooks in the Cheffile by doing:

librarian-chef install

Then I upload the haproxy cookbook to my Chef Server.

Hope that helps.

[mlavi]

I have also encountered this on CentOS 6.5 on master. :~(
With the above tip, I accomplished this with Berkshelf:

• cd chef-repo && cat Berksfile

source "https://supermarket.chef.io"
#metadata
#https://github.com/hw-cookbooks/haproxy/issues/109
cookbook "haproxy", github: "hw-cookbooks/haproxy", branch: "develop"

• berks update && berks vendor cookbooks
• knife cookbook upload haproxy --include-dependencies && knife cookbook list

Which resulted in a haproxy.conf file update when executed by Chef.

[alxndrmlr]

Got it working off the dev branch as well.

[michaelschlies]

I am working with organizations that need to pull from supermarket, pulling from branches via GIT isn't a viable solution. Is there anyway the haproxy_config LWRP can be merged into master?

[elijah]

This does indeed deserve to be merged and version bumped... please.

[ianrossi]

@elijah Are you asking for the develop branch to be merged to master?

[elijah]

It would certainly save me from a bunch of extra work hacking together a
sketchy version-bumped copy to upload to a very large organization's
supermarket. :-) [I'm not altogether certain that merely telling
Berkshelf to pull from the develop branch on github will work -- some
limitations on what I can force people to allow our pipeline to do.]

It would be appreciated :)

I found a few other weird things this afternoon, too - using an EPEL copy
of haproxy on fairly old AMI. Had to create user and group for haproxy by
hand in my recipe, because the RPM failed to do so... was going to PR that
and a few other things this evening, if I get a few moments.

--e

On Tue, Nov 8, 2016 at 4:58 PM, Ian D. Rossi [email protected]
wrote:

@elijah https://github.com/elijah Are you asking for the develop branch
to be merged to master?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#109 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACokznmdvbx5iqN5Y2epwT0YOUuT8Y4ks5q8P6jgaJpZM4FGdgd
.

[tas50]

Develop branch will go away soon

[ianrossi]

@elijah I didn't do a diff or anything but this a branch I had working that fixed a problem with the source install. I think this might have been merged, though. But has been working for me in production.
https://github.com/aimtheory/haproxy/tree/fix/install_source

[rshade]

@ianrossi can you see if this works on the latest version?

[damacus]

@ianrossi I'm going to close this issue now as we've significantly changed the way to cookbook configures things.
We'll not be doing any patches to v3.

If v4 does not work in some way please open a ticket.

Thanks!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.