Skip to content

Commit fcc6df9

Browse files
authored
Adding "custom" key to Seeding instructions
I had a misunderstanding on how the seeding configuration should be done. I suggest putting the root key `custom` in for less misunderstandings.
1 parent 5ff42c2 commit fcc6df9

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

README.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -120,23 +120,24 @@ If `dynamodb.start.seed` is true, then seeding is performed after table migratio
120120
If you wish to use raw AWS AttributeValues to specify your seed data instead of Javascript types then simply change the variable of any such json files from `sources:` to `rawsources:`.
121121

122122
```yml
123-
dynamodb:
124-
start:
125-
seed: true
126-
127-
seed:
128-
domain:
129-
sources:
130-
- table: domain-widgets
131-
sources: [./domainWidgets.json]
132-
- table: domain-fidgets
133-
sources: [./domainFidgets.json]
134-
test:
135-
sources:
136-
- table: users
137-
rawsources: [./fake-test-users.json]
138-
- table: subscriptions
139-
sources: [./fake-test-subscriptions.json]
123+
custom:
124+
dynamodb:
125+
start:
126+
seed: true
127+
128+
seed:
129+
domain:
130+
sources:
131+
- table: domain-widgets
132+
sources: [./domainWidgets.json]
133+
- table: domain-fidgets
134+
sources: [./domainFidgets.json]
135+
test:
136+
sources:
137+
- table: users
138+
rawsources: [./fake-test-users.json]
139+
- table: subscriptions
140+
sources: [./fake-test-subscriptions.json]
140141
```
141142

142143
```bash

0 commit comments

Comments
 (0)