DDN CLI: ddn command update

Update Commands in the local metadata.

Synopsis

When the underlying data source changes, it's necessary to update the command's metadata to ensure Hasura DDN is aware of any modifications. Typically, before updating a command, you'll have re-introspected the underlying data source.

ddn command update <command-name> [flags]

Examples

# Update all Commands using the subgraph set in current context
 ddn command update "*"

# Update the Command "Login" in the "app" Subgraph
 ddn command update Login --subgraph ./app/subgraph.yaml

# Update all the Commands in "app" Subgraph
 ddn command update "*" --subgraph ./app/subgraph.yaml

# Update Commands filtered by glob pattern in the Subgraph "app"
 ddn command 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 command - Perform Command-related operations