[ 
https://issues.apache.org/jira/browse/CASSSIDECAR-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paulo Motta updated CASSSIDECAR-429:
------------------------------------
    Summary: Add RFC 6902-inspired JSON Patch support to ConfigurationManager  
(was: Implement basic configuration update in ConfigurationManager)

> Add RFC 6902-inspired JSON Patch support to ConfigurationManager
> ----------------------------------------------------------------
>
>                 Key: CASSSIDECAR-429
>                 URL: https://issues.apache.org/jira/browse/CASSSIDECAR-429
>             Project: Sidecar for Apache Cassandra
>          Issue Type: Task
>          Components: Configuration
>            Reporter: Paulo Motta
>            Assignee: Paulo Motta
>            Priority: Major
>
> Implement patch operations for the Configuration Manager using RFC 
> 6902-inspired semantics: paths reference the effective configuration 
> structure but mutations target the overlay. Supported operations: add, 
> remove, replace, test. No move/copy.
> Key behaviors:
>  - Paths use JSON Pointer syntax for both top-level and nested cassandraYaml 
> keys
>  - Nested path mutations copy the entire top-level key from the effective 
> config into the overlay (copy-siblings strategy), ensuring the overlay is 
> self-contained at top-level key granularity
>  - test operations assert against the effective config without mutating
>  - replace fails if the path is absent from effective config (typo protection)
>  - remove fails if the path only exists in the base template (not in overlay)
>  - All operations are validated atomically before any mutations are applied
>  - JVM option key format and conflicting boolean option validation
> Version-aware schema validation, immutable settings blocklist, and failure 
> policy handling will be added in follow-up tasks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to