Skip to content
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: block init if amplify app creation fails #10839

Merged
merged 6 commits into from
Feb 9, 2023

Conversation

edwardfoyle
Copy link
Contributor

@edwardfoyle edwardfoyle commented Aug 3, 2022

Description of changes

Blocks amplify init if the Amplify App service limit has been reached. This prevents downstream errors and weird behavior where an Amplify App is expected to exist.

Issue #, if available

Fixes #10838

Description of how you validated changes

Tested locally, added unit test, E2E running here: https://app.circleci.com/pipelines/github/aws-amplify/amplify-cli?branch=run-e2e/foyleef/app-limit-init-block

Checklist

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@edwardfoyle edwardfoyle requested a review from a team as a code owner August 3, 2022 18:05
@codecov-commenter
Copy link

Codecov Report

Merging #10839 (2e4935b) into dev (f7e6b81) will increase coverage by 0.00%.
The diff coverage is 20.00%.

@@           Coverage Diff           @@
##              dev   #10839   +/-   ##
=======================================
  Coverage   47.43%   47.43%           
=======================================
  Files         673      673           
  Lines       33274    33275    +1     
  Branches     6724     6721    -3     
=======================================
+ Hits        15782    15784    +2     
  Misses      15803    15803           
+ Partials     1689     1688    -1     
Impacted Files Coverage Δ
...r-awscloudformation/src/amplify-service-manager.js 6.12% <20.00%> (+0.38%) ⬆️
...li/src/domain/amplify-usageData/getUsageDataUrl.ts 100.00% <0.00%> (+12.50%) ⬆️

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

danielleadams
danielleadams previously approved these changes Aug 11, 2022
@danielleadams danielleadams added the semver-major pull requests that have breaking changes and are not to be merged until release is started label Jan 18, 2023
@edwardfoyle edwardfoyle changed the base branch from dev to cdkv2 February 6, 2023 19:07
sobolk
sobolk previously approved these changes Feb 7, 2023
Copy link
Member

@sobolk sobolk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Please get clean e2e run before merging.

@sobolk
Copy link
Member

sobolk commented Feb 7, 2023

Could you split TS conversion into separate PR and get this also to dev ? Will help with merges if we're to stick with branch for a bit.

@edwardfoyle edwardfoyle merged commit 86550c3 into aws-amplify:cdkv2 Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver-major pull requests that have breaking changes and are not to be merged until release is started
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CLI should fail on init if app limit has been reached
6 participants