SeedManifest.
What the seed of a tenant reads and what each file becomes: the files with their hashes, the corpus and the window, the mapping of each file to the objects it makes
Figure 1SeedManifestspecified
- kind
- definition
- scope
- platform
- key
- the tenant and the version
- store
- postgres
- family
- market
Fields#
| field | type | required | note |
|---|---|---|---|
tenant | id | yes | |
version | count | yes | |
files | [json] | yes | path, hash, becomes |
corpus | text | yes | the shared corpus it reads |
window_months | count | yes | the parameter; one at first |
window_end | date | yes | the corpus’s most recent month |
Routes that use it#
No route takes or returns SeedManifest directly. The record holds it, and the objects that point at it reach it.