Early Access Program - limitations and known issues

Owned by Steffen Opel [Utoolity]
Last updated: 08.07.2023Version comment
4 min read

Welcome to our early access program (EAP) for Develop with AWS. We highly appreciate that you want to help shape the future of AWS DevOps integration with the Atlassian products and look forward to your feedback. Before you agree to join, please note the following limitations and known issues:

Join the EAPs

Develop with AWS is currently in the works and we hope to publish an EAP by mid March (Jira) and end of March (Compass) – if you are interested in these apps, feel free to join our …

Limitations

No guarantees

This is the actual app that we will publish to the Marketplace later on (hopefully by early April), so while there might still be some changes during the EAP if we encounter something unexpected, we intent and expect that you can just keep using the app and won’t have to reconfigure it after GA.

That being said, there are no guarantees that you won’t eventually have to reconnect environments for example, or need to replay already ingested events to address data alignment issues (we already retain your ingested events in an event bus archive, but do not yet surface the retention setting or replay capabilities due to being out of scope for the initial release).

Supported AWS services

Develop with AWS aims support many applicable AWS services and resource types, we have to start somewhere though and take it step by step (refer to Integrations for details) – specifically, the EAP will allow you to:

Note that CodeBuild action and CloudFormation action refer to using CodeBuild as a build or test action, and CloudFormation as a deploy action within a CodePipeline, i.e. standalone use of CodeBuild is out of scope for the initial release.

Known issues

Onboarding

The environment onboarding flow is fully automated via CloudFormation stacks, which has the following implications:

  • On first installation of the app, it takes about ~3.5 minutes to provision the required site specific tenant resources – we’ll provide better live feedback, but that’s blocked until some pending platform improvements will be available later this year.

  • Environments (account/region combinations) and connections (IAM roles) are currently configured together and therefore require admin permissions – we’ll split this into separate views and flows so that only the connections will require admin permissions, whereas environments can be connected by every team member

  • Environments and connections cannot yet be configured manually – based on resp. feedback, we’ll add a CRUD UI in the app so that these can be connected manually, and separately

  • Environments receive a default name derived from the action context (e.g. the CodePipeline pipeline name, or the CodeBuild project name) – we’ll add a tag based override option for starters

CodePipeline

The CodePipeline integration does not yet support:

  • Approval visualization – Approval steps are shown as ‘in progress’ rather than ‘pending’

CodeBuild

The CodeBuild integration does not yet support:

  • Standalone CodeBuild builds in Jira – CodeBuild events are only ingested when the build has been started from a CodeBuild build or test action within a CodePipeline pipeline, i.e. standalone use of CodeBuild is out of scope for the initial release.

  • Event backfilling in Jira – Events are only ingested once the integration is in place – we’ll add backfilling logic for past build events later on.

  • Test references – Information about tests that were executed during a build

  • Code references – Optional information that links a build to a commit, branch etc.

CloudFormation

The CloudFormation integration does not yet support:

  • Standalone CloudFormation deployments in Jira – CloudFormation events are only ingested when the build has been started from a CloudFormation stack deploy action within a CodePipeline pipeline, i.e. standalone use of CloudFormation is out of scope for the initial release.

  • Event backfilling in Jira – Events are only ingested once the integration is in place – we’ll add backfilling logic for past build events later on.

  • Stack Sets – We’ll tackle the separate CloudFormation stack set deploy action down the road

Jira

The Jira integration does not yet support:

  • shipped ‘Configure’ button in the the ‘Manage apps’ – we’ll add this one in the near future (in the meantime please click on the ‘Develop with AWS’ link in the left sidebar)

  • ‘Get started’ button in the the ‘Manage apps’ – we’ll add a get started experience in the near future

  • Issue key detection in branch names and pull request titles – so far the app only supports issue key detection in commit messages, we’ll amend this in a future release

  • Event backfilling – Other than with Compass, events are not backfilled once the integration is configured – this is a technical limitation that we'll address this in a future release

Compass

The Compass integration does not yet support:

  • shipped Event backfilling for larger projects – Events are not backfilled at all when there are more than 100 recent events

  • Event backfilling for larger projects – Events beyond 100 recent events are not backfilled – this is a technical limitation that we’ll address in a future release

  • Event backfilling for existing links – Events are only ingested once the integration is in place – we’ll add backfilling logic for past deployment events later on