[GEODE-10230] Support for PDX Update and Delete Endpoints in Management REST API

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.15.0
• Fix Version/s: 1.15.0
• Component/s: management, rest (admin)
• Labels: needsTriage pull-request-available
• Assignee: Juan Ramos
• Reporter: Juan Ramos
• Created: 11/Apr/22 11:01
• Updated: 22/Jun/22 20:45
• Resolved: 12/Apr/22 19:26

Description

Support for PDX Update and Delete Endpoints in Management REST API

The cluster management REST API only exports CREATE and DELETE operations for all currently supported configuration elements (region, gateway, pdx, etc.). Even though several of the ConfigurationRealizer, ConfigurationManager and ConfigurationValidator are already implemented, the LocatorClusterManagementService always throws an exception for UPDATE operations and the actual endpoints don't even exist on the respective controllers.
The above greatly limits the ability of consumers to use the management REST API endpoints as the configurations can't be changed after creation time, making some of them useless. As an example, a user probably doesn't know before hand the full list of domain classes that need to be serialized using the PDX auto-serializer. When using only the management REST API endpoints to manage a cluster, this implies that the PDX cluster configuration becomes useless as soon as an extra pattern needs to be added, forcing the user to entirely re-create and re-populate the cluster from scratch.

This ticket only aims to support delete and update operations for the PDX configuration using the management REST API, the rest of the configuration elements will remain forbidden (old behaviour will be kept by leveraging the respective ConfigurationValidator) and must be incrementally added in the future if needed.

Issue Links

• links to: GitHub Pull Request #7578