open-telemetry / open-telemetry/weaver
Document exact datamodel for values sent to REGO policies
Open
Nobody has claimed this yet.
policy engine
ux
- Dominant language
- Rust
- Stars
- 486
- Forks
- 108
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 40
Description
As part of a "getting started" guide, we should provide a tabular-type view of which fields (and their nested structure) are available in Rego policies, by namespace.
Related to #583
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 getting-started guide and review related issue #583. Identify the source of the values exposed to Rego policies, then organize the available fields and nested structure by namespace in a tabular view. Done means the guide documents the exact data model a reader can use in Rego policies.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100