open-policy-agent / open-policy-agent/java-opa-sdk
Per-bundle activation status events
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 24
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 15
Description
BundlePlugin reports a single aggregate bundles plugin status (OK, NOT_READY, ERROR) and notifies on activation, but per-bundle state isn't surfaced anywhere a Status plugin (#8) or operator could observe it. OPA Go publishes per-bundle status: last successful activation timestamp, current revision, last download/activation errors.
- Track per
BundlePlugin.Bundlelast successful activation time, last download error, last activation error, current revision (depends on #63 for revision exposure). - Expose via a typed accessor on
BundlePluginand as a status event the Status plugin can consume. - Surface activation-failure events from the rollback path (depends on #66).
- Tests: status reflects success, transient download failure, activation failure with rollback.
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 BundlePlugin's existing aggregate status and activation notification paths, then inspect how the Status plugin consumes status events. Review dependencies #63 and #66 before defining the per-bundle state; done means success, transient download failure, and rollback activation failure are represented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100