Skip to content

Commit 73ce16a

Browse files
author
Dane Pilcher
authored
Update data migrations (#8286)
* change data prop names * use latest data snapshot
1 parent ca52ab2 commit 73ce16a

File tree

1 file changed

+10
-10
lines changed
  • src/pages/[platform]/start/migrate-to-gen2

1 file changed

+10
-10
lines changed

src/pages/[platform]/start/migrate-to-gen2/index.mdx

+10-10
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ The most notable change between Amplify Gen 1 backends and Gen 2 backends is the
5454

5555
**Testers Only**
5656

57-
Prerequisites:
57+
Prerequisites:
5858

5959
- Node.js v18.17.1 or higher
6060
- [Local AWS CLI profile](/gen1/[platform]/start/getting-started/installation/) with `AdministratorAccess-Amplify` and the `AmplifyBackendDeployFullAccess` policies attached.
@@ -82,7 +82,7 @@ amplify add env migrate
8282

8383
<Callout info>
8484

85-
**Testers Only**
85+
**Testers Only**
8686

8787
For testing purposes, you will need to additionally install the tagged versions of the `@aws-amplify/cli` package.
8888

@@ -96,7 +96,7 @@ Then push your newly-created `migrate` environment to create a set of resources
9696

9797
<Callout info>
9898

99-
**Testers Only**
99+
**Testers Only**
100100

101101
If you have API resources, you will need to enable the following feature flag in your `amplify/cli.json` file:
102102

@@ -176,12 +176,12 @@ npm install
176176

177177
<Callout info>
178178

179-
**Testers Only**
179+
**Testers Only**
180180

181181
For testing purposes, you will need to additionally install the tagged versions of the `@aws-amplify/backend` and `@aws-amplify/backend-data` packages.
182182

183183
```bash title="Terminal" showLineNumbers={false}
184-
npm install @aws-amplify/[email protected]20250307211308 @aws-amplify/[email protected]20250307211308
184+
npm install @aws-amplify/[email protected]20250314161305 @aws-amplify/[email protected]20250314161305
185185
```
186186

187187
</Callout>
@@ -211,10 +211,10 @@ If you have GraphQL API, you would need to manually input your schema in `data/r
211211
```typescript
212212
import { defineData } from "@aws-amplify/backend";
213213
export const data = defineData({
214-
migratedAmplifyGen1DynamoDbTableMap: [
214+
migratedAmplifyGen1DynamoDbTableMappings: [
215215
{
216216
branchName: "sandbox",
217-
modelTableNameMap: {
217+
modelNameToTableNameMapping: {
218218
Post: "Post-xnibcobqircidcckd2zx2uzxgq-dev",
219219
Comment: "Comment-xnibcobqircidcckd2zx2uzxgq-dev",
220220
},
@@ -239,11 +239,11 @@ In order to provide a smoother experience with the migration tooling, we have ad
239239

240240
For example, if you have a Node.js Lambda function in Gen 1, you will see the following error in your sandbox run:
241241

242-
```bash title="Terminal" showLineNumbers={false}
242+
```bash title="Terminal" showLineNumbers={false}
243243
Source code for this function can be found in your Amplify Gen 1 Directory. See .amplify/migration/amplify/backend/function/app81ff331aPostConfirmation/src
244244
```
245245
246-
you will need to copy the code from your Gen 1 backend and make any necessary changes to the code such as updating to TypeScript and updating the import statements.
246+
you will need to copy the code from your Gen 1 backend and make any necessary changes to the code such as updating to TypeScript and updating the import statements.
247247
248248
**Note:** You will need to install the Lambda dependencies in the project root `package.json` file.
249249
@@ -369,7 +369,7 @@ Then redeploy the application by committing the changes to Git.
369369
370370
## Verify continuous deployment
371371
372-
After performing the post-migration tasks, commit your changes and allow your deployment pipeline to deploy changes without error.
372+
After performing the post-migration tasks, commit your changes and allow your deployment pipeline to deploy changes without error.
373373
374374
{/* what happens when you experience an error */}
375375

0 commit comments

Comments
 (0)