Configuration Service Invocation
Perform application-level configuration management.
Introduction
Manage application-level configuration by calling the Capa SDK API. The underlying implementation uses SPI to register adapter implementations for various platforms.
Invocation Logic
The following diagram shows the Capa Configuration service invocation logic:
- Service (appid:A): the service invoker, CloudX Configuration Service is the service being invoked, which can be any cloud vendor’s configuration service
- Service (appid:A) initiates a service call to the Cloud Configuration Service through the Capa SDK
- Capa Configuration API is a unified API specification
- Capa-CloudX Configuration Adaptor SDK is Capa’s adapter implementation class, registered via SPI
- CloudX Configuration Service provides the actual configuration service
API Design
The design of the Capa Configuration API follows community standards:
The meanings of specific parameters are as follows:
| Parameter | Meaning |
|---|---|
| storeName | Storage name |
| appId | Unique service ID within the same namespace |
| keys | List of configuration keys |
| metadata | Metadata for sending configuration requests |
| group | Configuration group (Optional) |
| label | Configuration label (Optional) |
| type | The specific type corresponding to the generic in the request response object |
| ConfigurationRequestItem | Request object |
| ConfigurationItem | Response object for getting configuration |
| SubConfigurationResp | Response object for subscribing to configuration |
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.