Skip to content

[compatibility improvement] Deprecate use of build-essentials and yum-epel cookbooks #90

@GitBytes

Description

@GitBytes

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions