-
-
Notifications
You must be signed in to change notification settings - Fork 244
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
Rewrite Consul cookbook to use custom resources #555
Comments
I totally agree here, but unfortunately do not have time to do it myself. |
I think its fair to assume major version breaking changes. 🏛️🚚 |
@johnbellone I've actually been working on a rewrite for this for a major version release that will leverage custom resources. It's been a long process thus far and I've had to refocus but hopefully be able to pick it back up |
Instead of doing a complete rewrite in a single commit, I'll suggest that we gradually migrate individual features (like consulDefinition) one at a time in separate releases. This will help us ensure backward compatibility and also reduce the probability of bugs. |
@theanirudhvyas that would normally be the best way but, after having gone through a lot of this cookbook, a complete rewrite is probably the most expeditious. |
Port resource to use Chef native framework, and drop deprecated poise dependencies. Specs are not ported since none were added for newest resources (policy/role/etc). Fixes sous-chefs#551 sous-chefs#555 sous-chefs#590
Port resource to use Chef native framework, and drop deprecated poise dependencies. Specs are not ported since none were added for newest resources (policy/role/etc). Fixes sous-chefs#551 sous-chefs#555 sous-chefs#590
Port resource to use Chef native framework, and drop deprecated poise dependencies. Specs are not ported since none were added for newest resources (policy/role/etc). Fixes sous-chefs#551 sous-chefs#555 sous-chefs#590
Port resource to use Chef native framework, and drop deprecated poise dependencies. Specs are not ported since none were added for newest resources (policy/role/etc). Fixes sous-chefs#551 sous-chefs#555 sous-chefs#590
Port resource to use Chef native framework, and drop deprecated poise dependencies. Specs are not ported since none were added for newest resources (policy/role/etc). Fixes sous-chefs#551 sous-chefs#555 sous-chefs#590
Port resource to use Chef native framework, and drop deprecated poise dependencies. Specs are not ported since none were added for newest resources (policy/role/etc). Fixes sous-chefs#551 sous-chefs#555 sous-chefs#590
Port resource to use Chef native framework, and drop deprecated poise dependencies. Specs are not ported since none were added for newest resources (policy/role/etc). Fixes sous-chefs#551 sous-chefs#555 sous-chefs#590
* Rewrite resources to get rid of poise Port resource to use Chef native framework, and drop deprecated poise dependencies. Specs are not ported since none were added for newest resources (policy/role/etc). Fixes #551 #555 #590 * Address review comments and remove poise remains * Move helper methods around * Clean DSL usage up, rename attribute * Use archive_file to extract consul binary * Reintroduce spec_helper Even with no spec, seems to make CI fail. * Update nssm constraint for Chef 17 * Change the way parameters are passed to resource in default recipe Resource blocks seem to not yield objects anymore. * Remove CircleCI and Danger config Co-authored-by: Jonathan Amiez <j.amiez@criteo.com>
🗣️ Foreword
Thank for taking the time to fill this feature request fully. Without it we may not be able to , and the issue may be closed without resolution.
:person_frowning: Problem Statement
This cookbook is a mess of custom libraries that are difficult to maintain.
❔ Possible Solution
We should rewrite the Consul cookbook to use Chef custom resources
➕ Additional context
#551
#515
The text was updated successfully, but these errors were encountered: