16 Dec 2013
icon | false |
---|
style | padding-bottom:0.8em |
---|
Updates for this release:
Table of Contents minLevel 3 exclude Release [1-9]\.[0-9]\.[1-9]+
Highlights
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
New tasks for AWS Elastic BeanstalkYou 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: |
Panel | ||||
---|---|---|---|---|
| ||||
'Make it so' option for the create/update CloudFormation |
actionsTo 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.
|
|
Details
This release addresses the following issues:
Stories
TAWS-133 - As a user, I want a task to create/rebuild/restart/update/swap/terminate an Elastic Beanstalk environment so that I can operate artifacts
TAWS-132 - As a user, I want a task to create/update/delete an Elastic Beanstalk application version so that I can manage artifacts
TAWS-131 - As a user, I want a task to create/update/delete an Elastic Beanstalk application so that I can target deployments
Improvements
TAWS-167 - Add Elastic Beanstalk environment id handling
TAWS-135 - Add a 'Make it so' option to the create/update/delete CloudFormation actions
TAWS-73 - Align template source radio buttons vertically
Updates
Release 2.2.6
2014-04-07
This release addresses the following issues:
Bugs
TAWS-229 - The S3 download action failed when just a single file matched the selection based on object key prefix match only
TAWS-227 - The EBS Snapshot, EC2 Image and EC2 Instance tasks improperly failed with a misleading
java.lang.NullPointerException
when targeting non existing resourcesTAWS-63 - The EC2 Image backup and delete actions failed with a
java.lang.NullPointerException
when used with an instance type and OS surfacing ephemeral storage in the created AMI
Release 2.2.5
2014-04-02
This release addresses the following issues:
Bugs
TAWS-217 (UAA-3) - The S3 upload action ignored the Target Object Key Prefix (affects release 2.2.4 only)
Utoolity classifies this regression as critical: it causes files being uploaded to the bucket root instead, thereby potentially overwriting preexisting identically named objects - users of the S3 upload action in release 2.2.4 are advised to update immediately and review their exposure to this regression to take corrective actions, if need be (upload activities not using a Target Object Key Prefix are unaffected).
Release 2.2.4
2014-03-27
This release addresses the following issues:
Improvements
TAWS-207 - The S3 task's upload/copy actions support the specification of object metadata via JSON
Supported HTTP headers like Cache-Control/Content-Encoding/Content-Type/...
S3 Canned ACLs (TAWS-119)
S3 Reduced Redundancy Storage (TAWS-118)
S3 Server-side Encryption (TAWS-100)
Bugs
TAWS-226 (UAA-4) - The S3 actions did not fail the build on transfer errors
Release 2.2.3
2014-02-15
This release addresses the following issues:
Improvements
TAWS-198 - The Elastic Beanstalk Environment task can create worker tier environments
TAWS-101 - All tasks feature a 'How to use this task' help link to the online documentation
Release 2.2.2
2014-01-14
This release addresses the following issues:
Bugs
TAWS-190 - The EBS Snapshot, EC2 Image and EC2 Instance tasks could yield an exception due to improperly accounting for the Eventually consistency of the AWS API
TAWS-189 - The CloudFormation Delete action required the template field to be populated via the Create or Update action first
Release 2.2.1
2013-12-18
This release addresses the following issues:
Improvements
TAWS-183 - The CloudFormation task now offers several samples via an inline dialog
Bugs
TAWS-182 - Elastic Beanstalk task names referred to Amazon rather than AWS
TAWS-181 - The Application and Application Version tasks lacked output variables
TAWS-179 - CloudFormation resource output variable values used the stack id (ARN) rather than its name