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

« Previous Version 6 Current »

As of Tasks for AWS 2.14, you can provide JSON or YAML based task parameters as code by referencing configuration files via URLs. You can reference a configuration file from the build working directory via the file:// protocol, or from a publicly accessible web location via the http:// and https:// protocols (this also allows to reference a configuration file from a private S3 bucket via a pre-signed URL).

Limitations

Only a single file can be referenced via URL, combining multiple URLs into one parameter field is not possible. This is not yet covered by the task validation though, we are tracking a resp. improvement as  UAA-414 - Getting issue details... STATUS . The issue also outlines a potential workaround:

If you require composing configuration files at build time, you can use a Bamboo Script task to combine the various references with applicable tools like jq and yq before reusing the resulting file in a task configuration.

Supported URL protocols

The following URL protocols are currently supported:

  1. file:// – you can reference a configuration file from the build working directory. The file:// protocol only supports absolute paths, which requires using the build-specific ${bamboo.build.working.directory} Bamboo variable to craft the URL, for example:
    • file://${bamboo.build.working.directory}/cloudformation.template
  2. http:// and https:// – you can reference a configuration file from a publicly accessible HTTP/HTTPS URL, for example:

Contextual entity variables

In addition to the substitution of regular Bamboo variables, some tasks also support the substitution of contextual entities via 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 Injecting contextual entity variables into task configurations for details.

  • No labels