Detect using execute to run msiexec
Open
Nobody has claimed this yet.
New Cop Proposal
- Dominant language
- Ruby
- Stars
- 112
- Forks
- 69
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 13
Description
What category of cop is this?:
Please try to select as few as possible.
- Deprecation - A cop that alerts to a deprecation in the Chef Infra Client
- Correctness - A cop that alerts when incorrect coding behavior is being used
- Sharing - A cop that alerts to missing functionality necessary for sharing cookbooks with others
- Style - A cop that alerts to a style best practice
- Simplification - A cop that alerts to ways code can be simplified through refactoring
- Effortless - A cop that alerts on code that must be resolved to move to the Effortless pattern
- Policyfiles - A cop that alerts on code that must be resolved to move to the Policyfiles pattern
Describe the new cop:
Chef has a built in resource for this so we should alert that a user should refactor to use the built in resource with proper idempotency.
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 reviewing existing correctness cops and their tests, then identify the entry point for detecting execute resources that invoke msiexec. Done means the cop reliably flags that pattern and points users toward Chef's built-in resource with proper idempotency; add focused tests for the detection and message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100