The Configuration service allows data as a resource. The configuration data consists of key-value pairs and supports String, Password, Integer, Long, Decimal, and Boolean data types.
The String value serves multiple purposes. For example, if you want to store binary data, such as a keystore, as part of a configuration, you can encode the data in Base64.
The Configuration service includes two interfaces. If the plug-in uses a Spring context, the interfaces are injected. If the plug-in does not use Spring, the interfaces are retrieved from the service registry. In this case, you need two more interfaces to retrieve an instance of the Configuration service.
| Service | Description |
|---|---|
| IEndpointConfigurationService | Creates, reads, updates, and stores configurations as Automation Orchestrator resources. |
| IEndpointConfiguration | Represents a single configuration that is stored as a Automation Orchestrator resource. |
| IServiceRegistryAdaptor | An entry point to the IServiceRegistry.
Note: Use this interface when the plug-in is not based on Spring.
|
| IServiceRegistry | A service locator that provides Automation Orchestrator services. |
