open-policy-agent / open-policy-agent/java-opa-sdk
Per-bundle status fields per OPA spec
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 24
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 15
Description
StatusPlugin.Status.buildStatusReport reports per-bundle {revision, active: true}. OPA Go's status payload has a richer shape under bundles.<name>: last_successful_activation, last_successful_download, last_request, code, message, metrics, plus the current revision. Without those, ops tooling that targets OPA can't consume the Java SDK's status without translation.
- Surface the per-bundle activation and download timestamps from
BundlePlugin(depends on bundles #68). - Include
codeandmessagefor the most recent error if the bundle is in a failure state. - Match OPA Go's field names exactly so existing dashboards/integrations work unchanged.
- Tests covering: healthy bundle, transient download failure, activation failure (interaction with bundles #66 last-good 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 at StatusPlugin.Status.buildStatusReport and inspect BundlePlugin's existing bundle state and error handling. Compare the per-bundle shape with OPA Go's status payload, then cover healthy, transient download failure, and activation failure with tests, including last-good rollback behavior from bundles #66 and the timestamp dependency in bundles #68.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100