DDN CLI: ddn model update
Update Models in the local metadata.
Synopsis
When the underlying data source changes, it's necessary to update the model's metadata to ensure Hasura DDN is aware of any modifications. Typically, before updating a model, you'll have re-introspected the underlying data source.
ddn model update <model-name> [flags]
Examples
# Update all Models using the subgraph set in current context
ddn model update "*"
# Update the Model "Album" in the "app" Subgraph
ddn model update Album --subgraph ./app/subgraph.yaml
# Update all the Models in the Subgraph "app"
ddn model update "*" --subgraph ./app/subgraph.yaml
# Update Models filtered by glob pattern in the Subgraph "app"
ddn model update "user*" --subgraph ./app/subgraph.yaml
Options
--ci Disables the use of context
-c, --context string Name of the context to use. (default <current_context>)
-h, --help help for update
--pattern string Pattern to detect targets. Can be 'glob' or 'literal'. (default "glob")
--subgraph string Path to Subgraph config file
Options inherited from parent operations
--log-level string Log level. Can be DEBUG, WARN, INFO, ERROR, or FATAL. (default "INFO")
--no-prompt Do not prompt for required but missing flags
--out string Output format. Can be table, json or yaml. (default "table")
--timeout int Request timeout in seconds [env: HASURA_DDN_TIMEOUT] (default 100)
Parent operation
- ddn model - Perform Model-related operations