Integration of Amplify LocalStack Plugin with Amplify Gen 2
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws, javascript
- Domain
- cloud, devops, documentation
Research direction
Start by reviewing the existing AWS Amplify CLI Gen 1 integration, then compare its configuration and deployment scripts with the AWS Amplify Gen 2 Backend project linked in the issue. Define the required compatibility changes and document setup and deployment instructions; done means Gen 2 users can deploy successfully and follow the updated documentation.
Written by the indexing model from the issue text.
Description
Request for Compatibility with AWS Amplify Gen 2 Backend
Is your feature request related to a problem? Please describe.
Currently, this project works with the AWS Amplify CLI (Gen 1) as per the documentation here. However, I would like to use it with AWS Amplify Gen 2 Backend.
Describe the solution you'd like
Please provide support for AWS Amplify Gen 2 Backend. This involves ensuring compatibility with the new backend infrastructure and updating the necessary scripts, configuration files, and documentation.
Describe alternatives you've considered
While it is possible to continue using Gen 1, the enhancements and improvements in Gen 2 offer better performance and new features which are beneficial for the project.
Additional context
Here is the link to the AWS Amplify Gen 2 Backend: Amplify Backend.
Ensuring compatibility will help users transition smoothly to the latest version of Amplify, taking advantage of the new features and improvements offered in Gen 2.
Suggested Changes:
- Update the configuration files to support Gen 2.
- Modify the deployment scripts to align with the new backend structure.
- Update the documentation to include instructions for setting up and deploying with Gen 2.
Thank you for considering this feature request.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from localstack/amplify-localstack
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
localstack/amplify-localstack#15 · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in localstack/amplify-localstack
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
light
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aemdemos/patients-stryker#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·