Amplify Backend Gen1 → Gen2 Migration (Beta) #14490
Replies: 4 comments 14 replies
-
|
Heads up folks we identified a code generation bug: #14492 It pretty elusive at the moment and doesn't happen on every app. If this happens to you, please let us know and share your setup. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Is there any reason why Flutter is not supported? Or is it untested yet |
Beta Was this translation helpful? Give feedback.
-
|
I didn't see anything mentioned about DataStore alternatives? Imho, that's a big deal for the app functionality. I would also try to have something like a high level map of features of gen1 to gen2 from admin perspective, otherwise it's easy to get lost how things function or what's their purpose, or where things managed. I wrote about migration path a while back from that point of view |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the update. I haven't tested yet, but off the top of my head we use lambda layers heavily (well we just have 1 layer but it's shared with multiple lambdas). So I think we can't test this migration until lambda layers is supported in gen 2? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Amplify team has launched a beta version of a flavor of the Gen1 CLI that adds support for migrating Gen1 backend environments to Gen2.
Caution
The migration tool discussed here is in early stages of development and SHOULD NOT be
executed on any production or mission critical environments. Only run it for testing
purposes on environments you can afford to delete.
Your feedback will significantly help the team improve and stabilize the tool. We welcome and encourage any feedback on the migration process:
Get started by following our migration guide. We are eager to hear what you think and incorporate your feedback in the upcoming versions!
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions