-
-
Notifications
You must be signed in to change notification settings - Fork 599
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
Installation enhancement #222
Comments
There's a special recipe for installing from a .deb file. I would like to keep any larger refactorings / reorganization of the cookbook to a new, fresh version, not this one. |
@karmi, is a rewrite of this cookbook underway? While I'm currently using the published version without complaint (and many thanks!), if there's help the community can provide in testing and providing PRs for a next gen version, I'd like to contribute. We can't have the Elasticsearch Puppet folks get all the love! 😉 |
@davidski Hah, thanks! :) It wasn't started yet, still in a planning stage... I'd like to lay the foundation first, and then it would be awesome to jump on it... I'll try to announce it loudly when something will be available for review and evaluation. |
As the installation could have some company requirement, I think that the installation part could be done in wrapper mode, and keep the configuration from the cookbook. It's for this, I suggest to skip the installation_part from your cookbook I will plan to add a node[:elasticsearch][:skip_intallation] with a default value to false The suggested patch is:
|
I can see how this is intriguing, but this makes everything about attributes totally crazy, doesn't it? :) The proper solution is to extract the recipes into smaller ones, and tie them together in the |
Im my fork I have do this to be able to install debian package You can see a version in my fork in the reset_branch |
Hi, Did you have time to check the change in the reset_branch branch ? With my change I can set with the tar mode (by default), nothing change. With pkg it includes your debian or rpm recipes do perform a debian and rpm installation. Regards, |
I would like to see any solution for this merged. |
Checking on status for this. :) |
Hello! We've re-written the cookbook using libraries that expose resources and providers, so you shouldn't see this problem on the newer version; it should be much easier to install from packages. We also include package installs in the test suites now. Hope this helps! |
Hello,
I have forked your cookbook. I'm trying to switch to your repository to avoid to maintain our cookbook and to have to check your change to report on your fork if needed.
I'm looking to write a wrapper, but I have an issue with our internal organization.
I have to install ES from debian packet located in our internal debian repository.
Do you think that is possible to have an attribute in you cookbook, to avoid to create the ES users, group and the ark installation from the default recipe ?
The wrapper part will be responsible of the installation phase.
If you agree with this I can perform a modification in your cookbook to do this.
Regards,
The text was updated successfully, but these errors were encountered: