From 89a57dc8e4f26c4169899dac0f3d312d29aa2f42 Mon Sep 17 00:00:00 2001 From: Martin Polanka Date: Sun, 20 Aug 2017 12:48:34 +0200 Subject: [PATCH] pipeline variables references --- Exercise-Configuration.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Exercise-Configuration.md b/Exercise-Configuration.md index 60c3da3..263bbd3 100644 --- a/Exercise-Configuration.md +++ b/Exercise-Configuration.md @@ -209,6 +209,7 @@ Important features: * Every port either have to have defined reference to variable or it has to be blank. Actual value (for example string) is not allowed in port. If variable name is declared in port it has to exist in variables table. * Connection between ports can be one-to-one or one-to-many from the perspective of output port. That means it is possible to have one output port which redirects variables to two or more input ports. Of course there has to be exception, it is allowed to have variable which is used only in input port, value of this variable has to be defined in pipeline variables table. +* Variables table in pipeline can contain references to external variables, these references can be directed to variables from environment configuration or exercise configuration. Variable is reference if it starts with the character '$', variable cannot be used inside variable value (textual value "hello $world", where world should be reference, is not allowed). If for some reasons is needed to use variable value which starts with dollar sign it has to be escaped with backslash, so this "\$1 million" is actual value and not a reference. ### Boxes