Versions Compared

Old Version 8

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

Saved on

compared with

New Version 9

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

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Renamed page, updated sections and marked excerpt.

...

Excerpt
All tasks 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.

...


Image Added

...

Panel

...

borderColor

...

#bbb

...

bgColor#eeeeee

On this page:

Table of Contents
maxLevel3
excludePopular.*

Panel
borderColor#bbb
bgColor#eeeeee

Related Pages:

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.

  • (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.
  • We are contemplating to evolve the current key/value based approach to one based on hierarchical JSON payloads, please watch/vote/comment on the following issue to guide our resp. roadmap:
    Jira Legacy
    serverJIRA (utoolity.atlassian.net)
    serverIdfac61c2e-db0a-39da-bb3c-e0dc0ef556f0
    keyUAA-92

Example

This example  illustrates the variable generation pattern:

  • variables have a dedicated prefix

...

  • like bamboo.custom.aws.*,

...

  • with *

...

  •  being a task specific prefix, e.g. bamboo.custom.aws.cloudformation.stack
  • variables referring to a collection of resources provide their ids in a semicolon separated list (i.e. the same format available on input), e.g. ${bamboo.custom.aws.ec2.instance.resources}

...

  •  with values i-a316b842;i-b4210842 (line 2)

  • you can refer to these variables from subsequent tasks via something

...

  • like ${bamboo.custom.aws.ec2.instance.resources.i-a316b842.PrivateDnsName} (line 6) - however, given script access to such a named resource is difficult, there is a shortcut to ease reusing the first (and often only) affected resource via something

...

  • like ${bamboo.custom.aws.ec2.instance.first.i-a316b842.PrivateDnsName} (line 19):

    Code Block
    languagetext
    linenumberstrue
    Creating common variables for 2 resources affected by task:
... bamboo.custom.aws.ec2.instance.resources: i-a316b842;i-b4210842
Creating resource variables for instance 'i-a316b842':
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.InstanceId: i-a316b842
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.State: running
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.PrivateDnsName: ip-10-0-0-241.ec2.internal
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.PrivateIpAddress: 10.0.0.241
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.PublicDnsName:
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.PublicIpAddress: null
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.LaunchTime: 20150716T080402Z
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.tags: Name
... bamboo.custom.aws.ec2.instance.resources.i-a316b842.tags.Name: taws-it-2.0.0
Creating resource variables for instance 'i-b4210842':
... <skipped>
Creating common variables for first resource affected by task:
Creating resource variables for instance 'i-a316b842':
... bamboo.custom.aws.ec2.instance.first.InstanceId: i-a316b842
... bamboo.custom.aws.ec2.instance.first.State: running
... bamboo.custom.aws.ec2.instance.first.PrivateDnsName: ip-10-0-0-241.ec2.internal
... bamboo.custom.aws.ec2.instance.first.PrivateIpAddress: 10.0.0.241
... bamboo.custom.aws.ec2.instance.first.PublicDnsName:
... bamboo.custom.aws.ec2.instance.first.PublicIpAddress: null
... bamboo.custom.aws.ec2.instance.first.LaunchTime: 	20150716T080402Z
... bamboo.custom.aws.ec2.instance.first.tags: Name
... bamboo.custom.aws.ec2.instance.first.tags.Name: taws-it-2.0.0

  • (info)

...

  •  variables are also available as environment variables in

...

  • the Script

...

  •  task for example, albeit named slightly different, e.g. $bamboo_custom_aws_cfn_stack_StringWithRegex (Unix)

...

  • or %bamboo_custom_aws_cfn_stack_StringWithRegex% (Windows)

  • (warning)

...

  •  variables are locally scoped and thus only reusable in subsequent tasks and not in other jobs/stages due to the implied concurrency, see the

...

Custom Variables

Some tasks also support the substitution of custom variables to ease composing unique names when operating multiple AWS resources at once, for example creating EBS snapshots from a set of EBS volumes, or EC2 images from a set of EC2 instances - refer

...

to Custom Variables

...

 for details.