15 August 2014
Highlights of this release:
Updates for this release:
Highlights
Support for Atlassian Bamboo
Use Identity Federation for AWS in Atlassian Bamboo to gain the following benefits:
- easy access to elastic agents via the AWS Management Console (see the User's Guide for details)
- reuse by other add-ons, such as Tasks for AWS
Cross Product Support
Dedicated Add-ons per Application
Bamboo and JIRA are each supported via a new dedicated add-on per Atlassian application due to Marketplace restrictions for cross-product add-ons:
- the former JIRA only add-on will be archived, but can technically be used in parallel to ease migrating to the new version (minor usability issues apply)
- the add-ons operate independent right now, i.e. credentials need to be managed separately for each and duplicated if desired - cross-product usage via application links is on our mid-term roadmap
System scoped AWS credentials
An AWS connector can now be denoted as System scoped and then used from elevated code (e.g. within another add-on) without an active user session to allow usage within Atlassian Bamboo's Tasks for example, as facilitated by Tasks for AWS.
REST API v2
The API has been upgraded to Globally Unique Identifier (GUID) based IDs to support secure configuration migration across instances and installations (see the Developer's Guide for details).
Details
This release addresses the following issues:
- Stories
- IFAWS-236 - As an administrator, I want to migrate configurations across instances/installations
- IFAWS-223 - As an administrator, I want to add credentials with system scope so that I can use them without a user session
- IFAWS-91 - As a user, I want federated AWS access in Bamboo
- Improvements
- IFAWS-253 - Add 'create first account' request popup to connector create page
- IFAWS-217 - Add link to IAM Policy Simulator
- IFAWS-139 - Improve UI of console login overview and error page
- Bugs
- IFAWS-247 - Fix/Improve connector filter usability bugs/issues