See TL-335 for details, but in short, we want to be able to define (Nuxeo Drive) application oriented properties and retrieve those values using a REST API.
The goal is to be able to use A/B testing or define which features/behaviors can the client-side application use or not.
New properties could be:
After retrieving such properties, they should be merged with one from the server configuration file (
The current endpoind, SERVER_URL/drive/configuration will be reused to retrieve a JSON of those properties. This will ease the deloyment on the client side where no changes will be required.
Take inspiration from
NXP-17673 to implement the ConfigurationService logic.
When done, accessing to the endpoint will:
- Retrieve "properties" from the old server's config and log a deprecation warning. We do not want to use that file anymore in a future release.
- Retrieve properties using the ConfigurationService.
- Merge properties together: properties from the CM will have the priority in case of duplicates.
- Return the final JSON.