open-policy-agent / open-policy-agent/java-opa-sdk
Trigger status push on plugin status change
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 24
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 15
Description
StatusPlugin only reports on the periodic schedule. OPA Go also pushes a status update whenever a plugin transitions state (e.g. bundle activation, download failure), so dashboards see transitions promptly instead of waiting up to a full interval.
- Hook into
PluginManager.updatePluginStatusso a status transition triggers an immediate report (debounced if multiple plugins change in a short window). - Don't reset the periodic schedule — the eager push is in addition to it.
- Make the eager-push behavior configurable (default on, matching OPA Go).
- Tests: state transition causes a report inside the debounce window; sustained transitions don't flood the upstream.
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 at StatusPlugin and PluginManager.updatePluginStatus to trace how periodic status reports are scheduled and how transitions are detected. Add tests for a transition reporting within the debounce window and for sustained transitions not flooding upstream. Done means eager pushes are configurable, enabled by default, debounced, and do not reset the periodic schedule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100