Versions Compared

Old Version 1

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

compared with

New Version Current

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Moved variable code blocks from table into variables section.

All documented Task actions support Bamboo variables, both substituting them within parameters for AWS resource management and defining them from created AWS resources.

Info
To empower advanced build and automation scenarios, it his highly recommended to become acquainted with Using Global, Plan or Build-specific Variables.

Variable Substitution

Variables are substituted in all Task configuration text fields (e.g. Stack Name, Template URL, Instance ID, Volume ID etc.).

Note
titleSensitive Data Masking

Tasks may emit sensitive data like credentials which are not supposed to surface in build logs - this can be achieved as follows:

  • if the variable key contains the phrase "password", the value will be masked with "********" in the build logs; for example, if the key is "password", "awsAccessKeyPassword" or "awsSecretKeyPassword", the build log will show the substituted value as "********"

Variable Definition

Variables are defined by most Tasks for reuse in subsequent Tasks, see Bamboo Variable Substitution/Definition for details, and each task's documentation for example log outputs.

tasks support Bamboo Variable Substitution/Definition - this task's actions generate variables as follows:

Info
A task's generated variables might get amended with respective AWS API additions over time - a live build log will always provide the most current variable shape accordingly.