-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
[compatibility improvement] Deprecate use of build-essentials and yum-epel cookbooks #90
Comments
build-essential can be dropped when we drop Chef 13 support, but we'll want to keep yum-epel around since that allows for a no touch setup of EPEL on hosts. It's used throughout the Chef community so removing it here doesn't accomplish much. |
Is there a set timeline for that to happen yet @tas50? Thanks! |
Also, to my point, my suggestion doesn't prevent Chef 13 from being compatible, there just might be the additional step of adding a dependency on the consumer side as they are able to transition from 13 > 14. |
I think we drag our heels on this one until April and deprecate it then. Along with Chef-13! :) Thanks for opening up an issue |
Works for me! Thanks guys! |
Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs. |
Cookbook version
2.0.5
/latestChef-client version
>= 14
Platform Details
Any supported
Scenario:
Trying to cut down on deprecation warnings (
build-essentials
cookbook) or manage Yum EPEL via other means more naturally.Steps to Reproduce:
Include resources or recipes per README in a Chef 14 environment, attempt to use the Chef 14 build-essential resources manage EPEL (or just yum in general) in other ways outside of the yum-epel cookbook.
Expected Result:
Less dependencies when implementing this cookbook for configuration and letting the implementor manage dependencies outside of this cookbook which should be focused on nrpe, not how one manages yum-epel or build-essentials.
Actual Result:
Unexpected and unpredictable cookbook resolution results, resource naming conflicts, potential cookbook bloat, deprecation warnings in every Chef run. That should about do it for now I think.
Recommendation:
Move any current requirements to the testing fixture area of the cookbook if possible and make a couple more assumptions that things exist before deploying and configuring nrpe services.
Thanks! =)
The text was updated successfully, but these errors were encountered: