You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/pages/[platform]/start/migrate-to-gen2/index.mdx
+62-42Lines changed: 62 additions & 42 deletions
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,19 @@ export function getStaticProps(context) {
31
31
32
32
Amplify migration tooling is available! In this guide we will walk through how to perform migrations for your backends from Amplify Gen 1 to Amplify Gen 2. The steps you will perform will be against a new Amplify Gen 1 backend environment, and a new Amplify Gen 2 environment. After the steps are performed, you will be able to merge the migration branch onto your existing branches to individually migrate with zero downtime.
33
33
34
+
The migration tooling supports all major categories of Amplify Gen 2:
35
+
36
+
- Auth
37
+
- Data (previously API > GraphQL API)
38
+
- Storage
39
+
- Functions
40
+
41
+
Please note not all resource configuration properties are supported, however the migration tooling will generate code with errors signaling where manual intervention is required.
42
+
43
+
{/* ## Feature Support Matrix */}
44
+
45
+
{/* big table of features */}
46
+
34
47
## Preparing for migration
35
48
36
49
The most notable change between Amplify Gen 1 backends and Gen 2 backends is the use of infrastructure as code with TypeScript. Preparing your environment for migration involves converting the configuration of your live Gen 1 backend resources to their Gen 2 equivalent written using TypeScript.
@@ -77,12 +90,16 @@ After this command completes successfully your `amplify/` directory is converted
77
90
78
91
## Validating the preparation
79
92
80
-
{/* how to handle the thrown errors in the code */}
93
+
The preparation command will add npm dependencies relevant to your Gen 2 backend in the root `package.json`. Before you begin with the validation, install dependencies:
81
94
82
95
```bash title="Terminal" showLineNumbers={false}
83
96
npm install
84
97
```
85
98
99
+
{/* how to handle the thrown errors in the code */}
0 commit comments