Add `chef outdated` to audit Policyfile.lock.json for outdated cookbooks
Open
Nobody has claimed this yet.
Status: Waiting on Contributor
- Dominant language
- Ruby
- Stars
- 18
- Forks
- 23
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
Analogous to bundle outdated and berks outdated
Addresses the problem that sometimes dep solvers can be overly clever and can find old versions of cookbooks which avoid e.g. diamond conflicts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing chef outdated command entry point and reviewing the behavior of bundle outdated and berks outdated. Then inspect how Policyfile.lock.json is read and how cookbook versions are resolved. Done means the command audits the lockfile and reports cookbooks with newer available versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100