Deploy integration test backends using amplify CLI in headless mode.

[rjuliano]

Issue #, if available:

Description of changes:

CDK App

CDK app that creates CodeBuild projects used to build and deploy amplify backends to support the various integration test scenarios for amplify-android.

CodeBuild assets

Scripts and other components used by the CodeBuild project. These scripts use the amplify CLI in headless mode to setup the amplify projects. Schema files are located under the schemas folder and are loosely grouped by the integration tests for each respective module in amplify-android

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[lgtm-com[bot]]

This pull request introduces 7 alerts and fixes 3 when merging 0837ec4ab8670b00dda630031f2eff871db060b9 into 6834d2f713813fd069061fea4c48b558924fdb60 - view on LGTM.com

new alerts:

• 7 for Unused import

fixed alerts:

• 3 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 7 alerts and fixes 3 when merging 5a170348eccf64397dc49a8ec647b4389016e3a2 into 6834d2f713813fd069061fea4c48b558924fdb60 - view on LGTM.com

new alerts:

• 7 for Unused import

fixed alerts:

• 3 for 'import *' may pollute namespace

[rjuliano]

Looks good!

For the schema files, can you name them like:

• events_api.graphql
• person_car.graphql
• team_project.graphql
• blog_api.graphql
• comments_blogs.graphql

Done.

Please be sure to update the high-level documentation, to mention the functionality that's available:

• ./README.md
• ./src/integ_test_resources/android/README.md

And add a new one under ./src/integ_test_resources/android/amplify/README.md (or one of the child dirs) that talks about howto setup the Amplify resources.

Yes...I'll work on that next.

Looks like we're at a point now where we can provision the API and DataStore AppSync dependencies, is that right? Cognito auth stuff, too?

Correct. That's currently what we are doing for the backends used by the DataStore and API tests. It configures Amplify apps with Auth and API since those two categories can be setup in headless mode via the CLI. Devs can also choose to deploy to their own account during development. I'll add instructions for that in the README.

Do we have a way to generate configuration files for this stuff? Maybe through amplify CLI, itself? Anyway, these are all questions I have as an interested customer of this work. It'd be great to get into a README.

Yes...we should be able to, but it's not currently automated. Right now, I'm manually copying the config files to the S3 bucket in the build account (which is different than the AWS accounts that host the backend). The integration tests just copy the files from there before running the build . I'm currently considering a couple options:

1. Publish the config files at the end of a successful build since those artifacts are already there as a result of using the CLI.
2. Use the Amplify CLI before running the integration tests to pull the configuration.

Both will require some level of cross-account permissions.

Depending on how far we are now, we should also update Amplify Android's CONTRIBUTING.md so that contributors (me, you, Susie Q) can run the tests in our own dev accounts.

Yes. That should definitely make its way into that guide.

[lgtm-com[bot]]

This pull request introduces 7 alerts and fixes 3 when merging ebaaafb8d402a41f6b69e7024df37be0ac6b9f2f into 6834d2f713813fd069061fea4c48b558924fdb60 - view on LGTM.com

new alerts:

• 7 for Unused import

fixed alerts:

• 3 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 7 alerts and fixes 3 when merging c81bb18382088efa32c6259f4dde34088e18600f into 6834d2f713813fd069061fea4c48b558924fdb60 - view on LGTM.com

new alerts:

• 7 for Unused import

fixed alerts:

• 3 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 7 alerts and fixes 3 when merging 6916b193120731d26e40f848c5b6dd25691f3d4a into 3bcce6bb1639e88dd7eb9ba1c525f444f163429e - view on LGTM.com

new alerts:

• 7 for Unused import

fixed alerts:

• 3 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 7 alerts and fixes 3 when merging c4ebbd2d9c4ce18d692574616a5682a8904d4588 into 3bcce6bb1639e88dd7eb9ba1c525f444f163429e - view on LGTM.com

new alerts:

• 7 for Unused import

fixed alerts:

• 3 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 7 alerts and fixes 3 when merging a457a28059ef9c29045735c8e2c1903519a1c55a into 3bcce6bb1639e88dd7eb9ba1c525f444f163429e - view on LGTM.com

new alerts:

• 7 for Unused import

fixed alerts:

• 3 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request fixes 3 alerts when merging 0cdd502bcbb5af2cb0692a399232591502b78b11 into 3bcce6bb1639e88dd7eb9ba1c525f444f163429e - view on LGTM.com

fixed alerts:

• 3 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 1 alert and fixes 3 when merging 7aad6bae918887d0fefeac6a89e0196cd86889d0 into 3bcce6bb1639e88dd7eb9ba1c525f444f163429e - view on LGTM.com

new alerts:

• 1 for Unused import

fixed alerts:

• 3 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 2 alerts and fixes 5 when merging 536ca370510a58167e44742711580e40d229d038 into f961f16c379daf577af02235339a8a5b09c1b9a9 - view on LGTM.com

new alerts:

• 1 for Unused import
• 1 for 'import *' may pollute namespace

fixed alerts:

• 5 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 2 alerts and fixes 5 when merging 2e6597bf9d134a0b46d2cafebf999a217fd5dcf5 into b962c57c9935c7f90e3bee69c257007f794f4eb9 - view on LGTM.com

new alerts:

• 1 for Unused import
• 1 for 'import *' may pollute namespace

fixed alerts:

• 5 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 2 alerts and fixes 5 when merging 5421bc44b2d2b3959fd77acdae236d66360083e8 into b962c57c9935c7f90e3bee69c257007f794f4eb9 - view on LGTM.com

new alerts:

• 1 for Unused import
• 1 for 'import *' may pollute namespace

fixed alerts:

• 5 for 'import *' may pollute namespace

[lgtm-com[bot]]

This pull request introduces 2 alerts and fixes 5 when merging 699b8728c12b76a61544ce3bb7218ee368dacd67 into eab10558f1880bf9565dfa1aaf50d47de48de667 - view on LGTM.com

new alerts:

• 1 for Unused import
• 1 for 'import *' may pollute namespace

fixed alerts:

• 5 for 'import *' may pollute namespace