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

Extend Chef.deprecated API so that it is useful for external users to add their own deprecations #9015

Xorima opened this issue Oct 22, 2019 · 1 comment


Copy link

@Xorima Xorima commented Oct 22, 2019

Core Chef Resource Checklist

Before suggesting a resource for inclusion please make sure your suggestion meets these criteria for resources built into Chef:

  • Automates an operating system component that ships by default on systems such as authentication, raid, disk partitions, firewalls, containers, or virtualization systems.
  • Does not attempt automate 3rd party applications such as database, web, or application servers, which are best suited for cookbooks due to their fast moving nature.

Describe the resource:

I would like a resource I can include in my recipes to mark them as deprecated, and so that all deprecations appear at the end of the run in a known part of the run.
Currently a lot of people use Chef::Log.warn but this is logged in the middle of the run and may be missed, having a deprecation resource would enable cookbook developers to mark parts of a cookbook as deprecated and have expected behaviour as to where they will display to users

Why should this be included out of the box?:

So I can continue to upgrade cookbooks to Custom Resources ;)

What operating systems would it run on?


Can We Help You Implement This?:



This comment has been minimized.

Copy link

@lamont-granquist lamont-granquist commented Oct 23, 2019

deprecations as a resource make no sense at all.

users could use the Chef.deprecated API just like we do, the only problem is that there's no useful API for dynamically adding classed to Chef::Deprecated in ways that the number doesn't collide. we also tightly couple that API to our own website for deprecations which users won't be able to submit issues to.

@lamont-granquist lamont-granquist changed the title Deprecation Resource Request Extend Chef.deprecated API so that it is useful for external users to add their own deprecations Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.