[
https://issues.apache.org/jira/browse/CAMEL-26836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-26836 started by Andrea Cosentino.
------------------------------------------------
> camel-opa - reload validated WASM bundles atomically
> ----------------------------------------------------
>
> Key: CAMEL-26836
> URL: https://issues.apache.org/jira/browse/CAMEL-26836
> Project: Camel
> Issue Type: Improvement
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Labels: authorization, camel-opa, component-audit
>
> h2. Problem / motivation
> WASM policy bundles are loaded when the evaluator is constructed. Operators
> cannot replace policy/data without recreating the endpoint or route.
> h2. Proposed scope
> Add explicit reload and optional managed watch support. Validate and warm the
> replacement before publishing it atomically, keep an immutable policy/data
> revision, drain old pools and expose the active revision/hash. Report failed
> reloads while retaining the prior validated snapshot under an explicit
> documented policy.
> h2. Acceptance criteria / validation
> * Concurrent requests use one coherent old or new snapshot.
> * Invalid bundle or data never replaces the active revision.
> * Test draining, shutdown, rapid reloads, entrypoint validation and
> health/diagnostic state.
> * Document operator-controlled distribution and stale-revision behavior.
> h2. References
> *
> https://github.com/apache/camel/blob/5686684cb418/components/camel-opa/src/main/java/org/apache/camel/component/opa/OpaWasmEvaluator.java#L106
> *
> https://github.com/apache/camel/blob/5686684cb418/components/camel-opa/src/main/java/org/apache/camel/component/opa/OpaEndpoint.java
> Source: read-only component audit at 5686684cb418. Recheck current main
> before implementing; historical references identify the audited code.
> _AI-generated by Codex on behalf of oscerd (JIRA: acosentino)._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
