-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
Create consul_directories in install_* recipes #40
Comments
@rstrox it's in I'm having a bit of a hard time understanding the way that you're using the cookbook that the order in which these directories are created is affecting you. Could you try to explain a bit more? Thanks! |
Thanks for the quick reply! My plan was to install consul early alongside a "base" set of other recipes, populate Is there a recommended workflow for bootstrapping a cluster if one does not already exist, and joining an existing cluster using Chef's search facility or similar? |
What do you think of moving the
consul_directories.each
block from_service.rb
to theinstall_*.rb
recipes? That way,consul::install_binary
could be run in an initial setup step, monitored services could be added to that directory, and later on the consul service could be enabled and started in a later step without needing to fuss with creatingnode['consul']['config_dir']
for every service.I'd be happy to create a PR if you'd like.
Thanks for this great cookbook regardless!
The text was updated successfully, but these errors were encountered: