Context parameters naming for Microservices Deployments - 6.4

Talend Real-time Big Data Platform Release Notes

EnrichVersion
6.4
EnrichProdName
Talend Real-Time Big Data Platform
task
Installation and Upgrade
EnrichPlatform
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend Data Preparation
Talend Data Stewardship
Talend DQ Portal
Talend ESB
Talend Identity Management
Talend Installer
Talend JobServer
Talend Log Server
Talend Project Audit
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio

During processing of context parameters for Microservices, be aware of the following two special topics that influence the processing of context parameter during the execution of Microservices. (only for Microservices but not for Talend Runtime)

  • Context parameter might be overwritten by OS environment variable which can lead to unexpected side effects. To avoid this, try to use unique names which are not in conflict with names you use in your OS environment.

    Among the following parameters, Spring Boot will take the OS environment variable as the first level variable of the highest priority. If you specified the variable with the same name as the system's, it will take system's.

    • Commandline arguments,

    • OS environment variables.

    • Application properties packaged inside your jar.

  • Context parameters with some characters, for example, underscore and numbers surrounded by underscores, will be treated according to the Spring Relaxed binding which can lead to unexpected behaviour for your Routes. See https://github.com/spring-projects/spring-boot/wiki/Relaxed-Binding-2.0 for the transformations and avoid these character and character combinations in your context parameter to prevent conflicts or use them accordingly to take advantage of this effect.