Documentation for Tasks for AWS 2.2 – 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

« Previous Version 5 Next »

16 Dec 2013

The Utoolity team is pleased to present Tasks for AWS 2.2 – this release adds a new task to create/update/rebuild/restart/swap/terminate AWS Elastic Beanstalk environments, adds new tasks to create/update/delete AWS Elastic Beanstalk applications and application versions and adds a 'Make it so' option to the AWS CloudFormation task's create/update actions.

Highlights of this release:

Updates for this release:

Highlights

New tasks for AWS Elastic Beanstalk

You can now facilitate Amazon Web Service's Platform as a Service (PaaS) offering AWS Elastic Beanstalk to quickly deploy and manage applications in the AWS cloud - this is enabled by three new tasks:

  • Create/Update/Delete AWS Elastic Beanstalk applications
  • Create/Update/Delete AWS Elastic Beanstalk application versions
  • Create/Update/Rebuild/Restart/Swap/Terminate AWS Elastic Beanstalk environments

'Make it so' option for the create/update CloudFormation actions 

To simplify common AWS CloudFormation usage scenarios, the Create stack action now allows to Update [the] stack, if it already exists.; similarly, the Update stack action allows to Create [the] stack, if it does not already exist.

Only shared options are supported

Please note that in both cases only the shared subset of options available for both actions is passed though to the 'Make it so' action - the more advanced options remain available via the dedicated tasks.

Updates

Release 2.2.1

This release includes the following improvements:

  • The CloudFormation task now offers several samples via an inline dialog

Also, this release fixes the following issues::

  • Elastic Beanstalk task names referred to Amazon rather than AWS
  • CloudFormation resource output variable values used the stack id (ARN) rather than its name
  • The Application and Application Version tasks lacked output variables
  • No labels