In some special cases it is necesarry to filter the global variables used inside the job execution, if the "inpursEnv" or "inpustTerraform" is not defined all global variables will be imported to the job context.
Copy flow:
- type: "customScripts"
step: 100
inputsEnv:
INPUT_IMPORT1: $IMPORT1
INPUT_IMPORT2: $IMPORT2
commands:
- runtime: "BASH"
priority: 100
before: true
script: |
echo $INPUT_IMPORT1
echo $INPUT_IMPORT2
$IMPORT1 and $IMPORT2 will be added to the job context as env variable INPUT_IMPORT1 and INPUT_IMPORT2
Other configuration Options.
Copy flow:
- type: "customScripts"
step: 100
inputsTerraform:
INPUT_IMPORT1: $IMPORT1
INPUT_IMPORT2: $IMPORT2
commands:
....
Import when importing the template
Copy flow:
- type: "terraformPlan"
step: 100
importComands:
repository: "https://github.com/AzBuilder/terrakube-extensions"
folder: "templates/terratag"
branch: "import-template"
inputsEnv:
INPUT_IMPORT1: $IMPORT1
INPUT_IMPORT2: $IMPORT2
inputsTerraform:
INPUT_IMPORT1: $IMPORT1
INPUT_IMPORT2: $IMPORT2
- type: "terraformApply"
step: 200
workspace env variables > importComands env variables > Flow env variables
workspace terraform variables > importComands terraform variables > Flow terraform variables