v1.0.1 - Hotfix IAM Role for Multiple Amplify Apps in same AWS Account

This release fixes an issue that can arise with additional Amplify Apps created in the same AWS Account, where CodeCommit is the selected git repository. In v1.0.0, a failure could occur during deployment of additional Amplify apps due to the name of the existing IAM Role from the initial deployment and the name for of the IAM Role to be created (current deployment) being the same value. The resolution to this was to add the app_name to the end of the IAM role. In iam.tf you'll see this change reflected.

iam.tf
name = "${var.amplify_codecommit_role_name}-${var.app_name}"
Ex.

app_name = "my-app"
amplify_codecommit_role_name = "amplify-codecommit"

IAM Role Name = "amplify-codecommit-my-app"

The alternative idea to this was to use the ID of the Amplify App which is a unique value, however this creates a circular dependency between the Amplify App and the IAM Role, since the Amplify App would be referencing the ARN of the IAM Role, and the IAM Role would be referencing the ID of the Amplify App.

When using this version (v1.0.1), ensure you have unique App Names for each of your Amplify Apps, or you will again have a conflict with an IAM Role of that name already existing. The console let's you actually have two apps that have the same name (as the actual app ids are unique) but as a best practice the names should be unique.

Initial release

🚀