How the Configuration Is Updated when IS_10.5_Core

When updating the configuration, if Microservices Runtime encounters an asset that does not exist and IS_10.5_Core_Fix7 or higher is applied, one of the following happens:

If the asset is one of the types that can be created through a configuration variables template, Microservices Runtime creates it using the supplied key-value pairs. Only a subset of all the properties for an asset can be set in a configuration variables template. Microservices Runtime uses default values for all other asset properties. For a list of assets that can be created via application of a configuration variables templates, see Creating New Assets with the Configurations Variable Template.

If an asset type cannot be created through a configuration variables template, Microservices Runtime ignores properties and values that do not correspond to existing assets on the Microservices Runtime.

During substitution or asset creation, Microservices Runtime sets values for properties that are specified in the template but not set on the Microservices Runtime. For example, suppose the configuration variables template file specifies the following for a JMS connection alias named myAlias:

If the Microservices Runtime contains a JMS connection alias named “myAlias” and that alias specifies a Connection Client ID value of “xyz”, at startup, Microservices Runtime substitutes “abc” for “xyz”. If the myAlias connection alias does not specify values for Username or Password, Microservices Runtime substitutes the values set in jms.myAlias.password and jms.myAlias.user in the application properties template for the JMS connection alias Username and Password fields.

Note:
The ability to add an asset via the configuration variables template is provided in PIE-65555, which is available in IS_10.5_Core_Fix7 and later.