-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(cli): better error message when trying to publish with CD configured in Amplify Console #7874
fix(cli): better error message when trying to publish with CD configured in Amplify Console #7874
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One nit, but LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
This was causing E2E test failures. Refs: #7874 Co-authored-by: Colin Ihrig <colihrig@amazon.com>
👋 Hi, this pull request was referenced in the v5.4.0 release! Check out the release notes here https://github.com/aws-amplify/amplify-cli/releases/tag/v5.4.0. |
… configured in Amplify Console (#7874) (#8106) * Revert "fix: handle case where there is no appId (#8049)" This reverts commit f7e62df. The commit being reverted builds on top of another commit that is being reverted. * Revert "fix(cli): better error message when trying to publish with CD configured in Amplify Console (#7874)" This reverts commit 4f03859. The commit being reverted causes a number of customer bug reports in verion 5.4.0. Co-authored-by: Colin Ihrig <colihrig@amazon.com>
👋 Hi, this pull request was referenced in the v5.5.0 release! Check out the release notes here https://github.com/aws-amplify/amplify-cli/releases/tag/v5.5.0. |
…red in Amplify Console (aws-amplify#7874) * fix(cli): add specific check for cd branches when running `amplify publish` fix aws-amplify#7486 * test(cli): add tests for hasCdBranches * refactor(cli): mockBranches explicit values set per-test
This was causing E2E test failures. Refs: aws-amplify#7874 Co-authored-by: Colin Ihrig <colihrig@amazon.com>
… configured in Amplify Console (aws-amplify#7874) (aws-amplify#8106) * Revert "fix: handle case where there is no appId (aws-amplify#8049)" This reverts commit f7e62df. The commit being reverted builds on top of another commit that is being reverted. * Revert "fix(cli): better error message when trying to publish with CD configured in Amplify Console (aws-amplify#7874)" This reverts commit 4f03859. The commit being reverted causes a number of customer bug reports in verion 5.4.0. Co-authored-by: Colin Ihrig <colihrig@amazon.com>
Description of changes
Running
amplify publish
will now error with "You have already connected branches to your Amplify Console app. Please visit the Amplify Console to manage your branches." when CD is configured in the Amplify Console, re #7486.Issue #, if available
fix #7486
Description of how you validated changes
amplify init
in new react projectmain
branch to frontend on Amplify Consoleamplify-dev publish
amplify init
another react projectamplify-dev publish
without adding hosting or connecting a branchyarn test
yarn lint
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.