open-policy-agent / open-policy-agent/java-opa-sdk
Replace Map<String,Object> manifest with typed model
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 24
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 15
Description
Bundle.manifest is Map<String,Object>, parsed from .manifest by the BundleParser SPI. Every consumer (manifest enforcement, status events, decision logs) has to navigate the untyped tree and re-validate field types. A typed model would centralize that and let the compiler catch field-name typos.
- Define a
Manifestvalue type withrevision,roots,metadata, and a place for delta indicators (#64) and signing fields (#39). - Have
BundleParserproduceManifestdirectly; keep the raw map only if needed for round-tripping. - Update
Bundle,BundlePlugin, and downstream consumers. - Should land before — or alongside — #63, #64, #68 to avoid each one inventing its own ad-hoc accessors.
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 Bundle.manifest and the BundleParser SPI, then trace manifest enforcement, status events, decision logs, BundlePlugin, and downstream consumers. Define the Manifest shape around revision, roots, metadata, delta indicators, and signing fields, and update the listed consumers so typed access replaces ad-hoc map navigation; completion means the affected components use the model consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100