Document Policy as Code and the cookbook as the policy vessel
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 143
- Forks
- 438
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 16
Description
Is your feature request related to a problem? Please describe.
Policy as code. Policy as code. Policy as code.
Describe the solution you'd like
We currently say Policy in our menu, but we need to talk about Policy as Code as a concept. In this world the cookbook is the vessel for Infra and Compliance/Security policy. This requires reworking how we describe cookbooks, recipes, and compliance phase.
Describe alternatives you've considered
Additional context
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
The issue names no files, tests, or specific entry points. Start by reviewing the current Policy menu and documentation for cookbooks, recipes, and the compliance phase; done requires an agreed scope and updated explanations of Policy as Code and the cookbook as its policy vessel.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100