Skip to content
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

Open
GitBytes opened this issue Mar 21, 2019 · 6 comments

Comments

@GitBytes
Copy link
Contributor

Cookbook version

2.0.5/latest

Chef-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! =)

@GitBytes GitBytes changed the title [compatibility bug] Deprecate use of build-essentials and yum-epel cookbooks in metadata [compatibility bug] Deprecate use of build-essentials and yum-epel cookbooks Mar 21, 2019
@tas50
Copy link
Contributor

tas50 commented Mar 21, 2019

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.

@GitBytes
Copy link
Contributor Author

Is there a set timeline for that to happen yet @tas50? Thanks!

@GitBytes
Copy link
Contributor Author

GitBytes commented Mar 21, 2019

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.
This would just be an additional dependency added to the test side only in the case of Chef 13 for example.

@GitBytes GitBytes changed the title [compatibility bug] Deprecate use of build-essentials and yum-epel cookbooks [compatibility improvement] Deprecate use of build-essentials and yum-epel cookbooks Mar 21, 2019
@damacus
Copy link
Member

damacus commented Mar 21, 2019

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

@GitBytes
Copy link
Contributor Author

Works for me! Thanks guys!

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Sep 30, 2020
@xorimabot xorimabot removed the Stale label Sep 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants