Appdynamics / Appdynamics/appdynamics-cookbooks
Consider implementing resources and providers
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
There's been a trend in the chef community to implement library cookbooks for anything that is intended to be consumed by other cookbooks downstream. In short, resources and providers are much easier to consume (and extend, adapt, modify) downstream than recipes.
You can see this trend in the [most popular community cookbooks](https://supermarket.chef.io/cookbooks?order=most_downloaded), such as mysql, apache2, redisio, newrelic, and git.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points to inspect. Clarify which resources and providers are in scope and what completion should mean before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100