sharedConfigs
If the application supports sharedConfigs, then the application users
can define sharedConfigs in configuration which may be referred to and
reused across different services. The sharedConfigs
section is
therefore optional.
If provided, then the sharedConfigs section is a JSON array of sharedConfig definitions (JSON objects). Each corresponding to a sharedConfig type, as supported by the application. Each sharedConfig has the following parameters:
Key | Description |
---|---|
|
A unique name for the sharedConfig. |
|
The name of a sharedConfig type supported by the application. |
|
A free format description of the sharedConfig. |
|
The sharedConfig configuration. This is a JSON object with a
single |
Example: sharedConfigs
section
"sharedConfigs": [
{
"sharedConfigName": "APACConnectionDetail",
"sharedConfigType": "CONNECTION_DETAIL",
"description": "Shared configuration containing connection details to backend in APAC region",
"config": {
"application": {
"url": "www.apac.com",
"port": 3434
}
}
},
{
"sharedConfigName": "USConnectionDetail",
"sharedConfigType": "CONNECTION_DETAIL",
"description": "Shared configuration containing connection details to backend in US region",
"config": {
"application": {
"url": "www.us.com",
"port": 9009
}
}
}
]