chore: move Gen-1 API plugin to LTS branch #2744
Merged
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.
Description of changes
Removes the following Gen-1 related packages:
amplify-category-api
amplify-util-mock
amplify-dynamodb-simulator
amplify-graphql-transformer-migrator
amplify-schema-validator
(owned by Console team and used in Gen-1 flows)Bumps the major version for packages common to LTS branch and
main
including the V2 transformers. The new major version will have active feature development going forward.Verified that version bumps are as expected:
Test updates:
CI updates:
mock-e2e-tests
jobsplit-e2e-tests
script and re-generate the E2E workflow codebuild spec.Due to the volume of changes, this PR mostly has only package, test deletions which can be seen better from the left-side file navigation view during review. The follow-up PR would have the changes necessary to bump the version of transformer packages common to Gen-1 and CDK/Data constructs.
CDK / CloudFormation Parameters Changed
Issue #, if available
Description of how you validated changes
Full E2E test run passes except following -
sql_iam_access
,rds_pg_field_auth_userpool_iam
,sql_pg_models
andRelationalWithAuthV2Redacted
. These are due to unrelated test issues like account hitting resource limits. Re-trying and investigating some.Verified using local publish via verdaccio and consuming the updated package version in
amplify-backend
repo that I'm able to build and run unit tests.Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.