aws-amplify / aws-amplify/amplify-cli
(gen2-migration) `analytics` category (pinpoint)
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### Is this feature request related to a new or existing Amplify category?
_No response_
### Is this related to another service?
_No response_
### Describe the feature you'd like to request
Support migrating analytics pinpoint resources: https://docs.amplify.aws/gen1/react/build-a-backend/more-features/analytics/set-up-analytics/
### Describe the solution you'd like
https://docs.amplify.aws/react/build-a-backend/add-aws-services/analytics/set-up-analytics/
### Describe alternatives you've considered
None
### Additional context
_No response_
### Is this something that you'd be interested in working on?
- [ ] 👋 I may be able to implement this feature request
### Would this feature include a breaking change?
- [ ] ⚠️ This feature might incur a breaking change
Contributor guide
Research direction
Start by comparing the linked Gen 1 and Gen 2 analytics setup documentation for the migration behavior required for Pinpoint resources. Trace the Amplify CLI's existing gen2 migration entry points and analytics handling, then define completion as supporting migration of Pinpoint analytics resources consistently with the Gen 2 documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- analytics, cli, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100