Configuration Variables Template
A configuration variables template contains configuration properties that map to properties on the Microservices Runtime. You can set the property values externally in the template and then pass the values to a Microservices Runtime when it starts up. As part of the startup process, Microservices Runtime loads the information from the configuration variables template and replaces the configuration information stored in the file system.
By externalizing configuration information, you can use a single Docker image created for a Microservices Runtime across multiple environments, including different stages of the production cycle. For example, you might use different templates for specific environments such as testing versus production, or you might use the same template for all environments but use environment variables to vary the configuration in each environment.
A configuration variables template is a properties file that contains configuration data as a series of key-value pairs where the key name reflects the asset and particular asset property for which you can supply a value. For example, cloudstreamsconnection.AssetsPackage.xyzConnections\:s_conn1.connectionconfiguration.cn..connectTimeout=180000 indicates that the cloudstreamsconnection alias named as xyzConnections under the namespace xyzConnections\:s_conn1 is available in the package named AssetsPackage, and has a connection timeout of 180000.
The configuration variables template contains key-value pairs for only a subset of the microservices container configuration, that is, the configuration variables template does not include key-value pairs for all of the configuration information for a microservices container. Only some configuration information is supported for use with the configuration variables template. For example, for a OAuth token alias, the configuration variables template lists a key-value pair for the accessToken, accessTokenSecret, clientSecret, instanceUrl, refreshToken, and refreshUrl properties but the template omits key-value pairs for other properties, for example, the OAuth version.
When a configuration variables template is generated from an existing Microservices Runtime, the template is populated with configuration data from the Microservices Runtime instance. The template content reflects the Microservices Runtime configuration at the time Microservices Runtime generated the template.
Note:
For more information about microservices and configuration variables templates, see the Developing Microservices with webMethods Microservices Runtime document.
The following is an extract of the CloudStreams configuration variables template:
#Sample Generated Template
#Fri Aug 24 17:42:12 IST 2018
cloudstreamsconnection.AssetsPackage.xyzConnections\:s_conn1
.connectionconfiguration.cn..clientKeyAlias=
cloudstreamsconnection.AssetsPackage.xyzConnections\:s_conn1
.connectionconfiguration.cn..connectTimeout=180000
cloudstreamsconnection.AssetsPackage.xyzConnections\:s_conn1
.connectionconfiguration.cn..enableCompression=false
cloudstreamsdatabaseconfig.DatabaseConfig.pg.PgMenConfiguration
.perfDataEnabled=true
cloudstreamsdatabaseconfig.DatabaseConfig.pg.PgMenConfiguration
.reportInterval=100
cloudstreamsdatabaseconfig.DatabaseConfig.pg.jdbc.active=false
cloudstreamsdatabaseconfig.DatabaseConfig.pg.publish.events=false
cloudstreamslargefileconfig.LargeFileConfig.wst.largedata
.binaryStreamEnabled=true
cloudstreamslargefileconfig.LargeFileConfig.wst.largedata
.threshold=1234567
cloudstreamsoauthtokens.testOAUTH1.accessToken={AES}
LZx9vaF8gghTDI8YtM7Nxg\=\=
cloudstreamsoauthtokens.testOAUTH1.accessTokenSecret={AES}
tPtnGY6q6jsq/Kc3nqCQ5g\=\=
cloudstreamsoauthtokens.testOAUTH1.clientId=asdfdsfdsfds
cloudstreamsoauthtokens.testOAUTH1.clientSecret={AES}
eEE9SiDm81GM4FS6+1McAQ\=\=