Overview of Generic Configuration
This section provides you an overview and lists the services that Generic Configuration microservice provides for product and marketing managed information.
The Generic configuration microservice is used to store all the configuration files in a centralized location so that you can fetch and use it in the application.
Configuration files are grouped and saved in generic configuration microservice. Whenever you require a configuration file, you can call the generic configuration microservice and get the latest configuration file for the application.
There are four APIs available in the generic configuration microservice:
- POST is used to store configuration file into microservice with base64 file format.
- PUT is used to edit the configuration file.
- GET (configuration file) is used to retrieve the configuration file using group id and version id.
- GET (Group configuration file) is used to retrieve list of configuration files available under the group.
This microservice provides the following services.
- It is used to store the configuration file and all configuration versions.
- Configuration files can be grouped into group ID.
- You can retrieve the configuration files with various versions using the version ID.
- You can retrieve a list of configuration files under the group.
- It stores .property, .json and .xml files.
This microservice provides the following features.
Generic Configuration Management API Interface
Generic Configuration Service provides a centralized configuration service supported across applications to manage their configurations using API-based interface. This microservice supports distributed deployment and provides a stateless API interface. It has a data store (database) to persist configurations uploaded through the API interface.
Versioned Artifact
Every configuration file in the configuration microservice is maintained as a versioned artifact. Under each configuration group, applications are allowed to maintain more than one configuration content using a unique Config name.
Get Configuration API
The Get Configuration API retrieves the following information.
- Get Configuration based on Config Name: Get configuration file based on the group name and configuration where version ID is not a mandatory. If the version is not sent, then client receives the latest version for the configuration file content.
- Get List of Configurations managed under a Configuration Group: It provides the list of latest configuration names managed under the provided configuration group.
Addition of a New Artifact
The POST API allows the application to add a new configuration content under a given configuration group along with the associated version ID. If the version input is not provided, microservice automatically creates or increments the version.
Modification of an Existing Artifact
The PUT API allows the client application to update the file content to the existing configuration content. If the version is not provided, the latest version for the configuration content gets updated.
In this topic