Highlights (Core)
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Use the Put CloudWatch Events actionYou can now use the Put CloudWatch Events action to relay Bamboo notifications, Jira workflow transitions, and Jira Service Desk automation rule executions via Amazon CloudWatch Events so that you can match events and route them to one or more target functions or streams. This allows you to decouple the capturing of events like Jira Service Desk approvals, Jira workflow transitions or Bamboo plan executions from the decision to trigger subsequent automation by one or more target services:
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Specify the target region for actionsSo far, we have deduced the AWS region from the payload content (e.g. an SNS topic ARN), falling back to the AWS SDK default region in case this was not possible. This turned out to be a bit inflexible for services that do not require or support a region specification in a target resource, for example the as of today single regional event bus for CloudWatch Events, or the regional SMS offering for Amazon SNS. We have opted to introduce the well-established region selection widget to address these scenarios and cover possible mismatches via validations instead.
|
Highlights (Bamboo)
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Use plan, result and deployment entity variables in Bamboo notification recipientYou can now use dedicated contextual entity variables for the Plan, the ResultSummary, and the DeploymentResult within the Automate with AWS notification recipient to compose the payload when running remote actions with AWS from Bamboo notifications, specifically from plan level and system level notifications. Previously, you only had access to Bamboo's pre-formatted Notification entity, requiring you to parse values like the build number from text messages. It is now much easier to pass exactly the desired data to your remote actions, which can then easily compose custom messages in any conceivable target format with custom code or based on your favorite template engine. |
Resolved issues
Release 1.3.1
2018-04-25
This release addresses the following issues:
Core
Bugs
AAWS-464 – Fix surrogate event timestamp ISO 8601 format
Release 1.3.0
2018-04-24
This release addresses the following issues:
Core
Stories
AAWS-331 – As a user, I want to put a CloudWatch event so that I can trigger rules
Improvements
AAWS-206 – Add region selection widget
AAWS-423 – Surface support for additional Step Functions regions ap-southeast-1 and ca-central-1
Bamboo
Improvements
AAWS-355 – Add Bamboo plan entity variable to notification recipient
AAWS-356 – Add Bamboo result summary entity variable to notification recipient
AAWS-357 – Add Bamboo deployment result entity variable to notification recipient
Bugs
AAWS-409 – Fix region logged by Automate with AWS task always being null
Tasks
AAWS-378 – Drop support for Bamboo 5.10
Jira
Tasks
AAWS-377 – Drop support for Jira 7.0