open-telemetry / open-telemetry/weaver
Weaver needs to add some facilities to test the policies
Open
Nobody has claimed this yet.
policy engine
- Dominant language
- Rust
- Stars
- 486
- Forks
- 108
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 40
Description
To properly and fully test our policies, we need deeper integration in Weaver instead of relying solely on OPA for the tests. The reasoning is as follows:
- The names of the policy packages are meaningful for Weaver (i.e.
before_resolution,after_resolution, ...), unlike with OPA, so ideally, we need to check that as well. - The Rego extensions that we are likely to introduce in Weaver over time will only be testable within Weaver.
- While not specific to Weaver, in addition to the tests, we could combine both tests and Rego code coverage to aid the policy review process (code coverage is supported by Regorus).
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 Weaver, OPA, and Regorus but no files, tests, or entry points. Start by locating Weaver’s current policy-test integration and how policy package names are handled. Define the expected Weaver-level checks and coverage behavior, then verify that policy tests exercise named packages and report coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100