Attribute precedence and kitchen test runs
Open
Nobody has claimed this yet.
Aspect: Documentation
Component: Chef Infra Client
- Dominant language
- HTML
- Stars
- 143
- Forks
- 438
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 16
Description
In section Syntax for "suites" the key "attributes" is mentioned.
Each suite_name grouping may specify attributes as a Hash: { foo: "bar" }
However, the attribute precedence is not mentioned. TBH, I am not sure if and how attribute precedence applies to the kitchen run.
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 with the linked Syntax section for "suites" and the attribute precedence documentation, then investigate how attributes are handled during a Kitchen run. Done means documenting whether and how attribute precedence applies to suite attributes, with the relevant explanation added to the Kitchen syntax documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100