Web Application - Module 1 - Inconsistent expectations set on scope of GitHub account access required by Amplify

[ckamps]

When following the "Connect app..." workflow in the Amplify Console with a GitHub.com repository, it's clear that the Amplify Console requires more than just read only access to the user's GitHub account yet the Amplify console sets conflicting expectations and the workshop module's README.md does not set the degree of access expectations with the user so that the user can make a more informed decision.

This issue has also been filed in the aws-amplify organization on GitHub.com:

aws-amplify/amplify-hosting#329

Background

1. When selecting GitHub.com, the Amplify console states: "Amplify Console requires read-only access to your repository."

2. However, in the next step of the Amplify wizard, far more than just read only access to the user's repository is specified: "This application will be able to read and write all public and private repository data." i.e. the dialog implies that Amplify is requesting read and write access to all repositories, public and private, in the user's GitHub.com account.

Recommended Fixes

1. Given these inconsistencies in the Amplify UI, the workshop module's documentation should accurately set the user's expectation concerning the degree of access required so that the user can make an informed decision.

Many users should and will decline to allow such broad write access to their GitHub account.

2. Amplify's issues database should be reviewed to see if the inconsistent guidance is already filed as a bug. If it is not already filed, then a bug report should be filed.