add create and delete BackendEnvironment #61
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joekiller
force-pushed
the
create-backend-environment
branch
4 times, most recently
from
e3feaa7 to
060deff
Compare
- if given an amplifyAppId and amplifyEnvironment, then created the associated backend environment - ensure amplify environment name is valid - ensure exception tests are properly accounted for - add more details for AmplifyExportedBackendProps - make AmplifyCategoryNotFoundError a little more clear - emulate root stack cfn parameters that cli uses
joekiller
force-pushed
the
create-backend-environment
branch
from
060deff to
59d2d0f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
if given an amplifyAppId and amplifyEnvironment then created the associated backend environment
Fixes: aws-amplify/amplify-cli#12350