Automation with AWS 1.10 Release Notes

Highlights (Core)

Integrate distributed workflows with the Start Synchronous Step Functions Execution action

In addition to the asynchronous Start Step Functions Execution action, you can now also use the Start Synchronous Step Functions Execution action to process Bamboo notifications, Jira workflow transitions and Jira Service Management automation rule executions remotely with AWS Step Functions:

Synchronous Express Workflows allow developers to quickly receive the workflow response without needing to poll additional services or build a custom solution. This is useful for high-volume microservice orchestration and fast compute tasks that communicate via HTTPS.

Evaluate remote conditions with the Start Synchronous Step Functions Execution action

You can now use the Start Synchronous Step Functions Execution action in applicable integrations to evaluate arbitrary remote conditions by returning a JSON result shape that adheres to the action response format schema:

1 2 3 4 { 'result': false, 'errorMessage': "Deployment blocked due to service being in alarm state" }

This allows you to call AWS services and third-party REST APIs to ensure that any prerequisites for your workflows are automatically checked right before dependent steps are initiated.

Supported integrations are the Jira Service Management Automate with AWS if condition, the Jira Automate with AWS workflow condition and Automate with AWS workflow validator, and the Bamboo Automate with AWS task.

Highlights (Bamboo)

Use the app with clustered Bamboo Data Center deployments

You can now also use the app with clustered Bamboo Data Center deployments to gain the flexibility and administrative control to manage mission-critical Bamboo sites.

Upgrade task for private secret keys

Previously, the app stored private secret keys used for encrypting long-term AWS security credentials in the local home directory. This worked fine for non-clustered (single node) usage, and clustered usage has still been possible by manually performing the few steps required to migrate the keys to the new Bamboo Data Center shared home directory.

To remove these manual steps, an upgrade task now automatically migrates the private secret keys from the local home to the new Bamboo Data Center shared home directory – this should be a quick and seamless process, refer to https://utoolity.atlassian.net/wiki/spaces/IFAWS/pages/2911633589/Identity+Federation+for+AWS+2.15+Upgrade+Notes#Upgrade-task-for-Bamboo-home-migration for details.

Resolved issues

Release 1.10.0

2021-08-18

This release addresses the following issues:

Core

  • Stories

    • AAWS-842 – As a user, I want to start a synchronous Step Functions execution so that I can coordinate distributed workflows

    • AAWS-843 – As a user, I want to start a synchronous Step Functions execution so that I can check remote conditions

  • Improvements

    • AAWS-569 – Update to new AWS Architecture Icons

Jira

  • Tasks

    • AAWS-834 – Drop support for Jira 7.13

    • AAWS-884 – Drop support for Jira 8.0

    • AAWS-888 – Drop support for Jira 8.1

    • AAWS-891 – Drop support for Jira 8.2

    • AAWS-894 – Drop support for Jira 8.3

Bamboo

  • Stories

    • AAWS-910 – As an operator, I want compatibility with Bamboo Data Center so that I gain high availability

  • Tasks

    • AAWS-831 – Drop support for Bamboo 6.7

    • AAWS-883 – Drop support for Bamboo 6.8

    • AAWS-892 – Drop support for Bamboo 6.9