Documentation for Tasks for AWS 2.12 – other releases are available in the Tasks for AWS Documentation Directory.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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

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.).

Sensitive 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.

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.

  • No labels