DDN CLI: ddn connector init
Add a new Connector.
Synopsis
Add a new Connector
ddn connector init <connector-name> --hub-connector <connector-type> [flags]
Examples
# Initialize a Postgres Connector "mydb" in the Subgraph "app"
ddn connector init mydb --subgraph ./app/subgraph.yaml --hub-connector hasura/postgres
# Initialize a Postgres Connector "mydb" inside the directory ./connector
ddn connector init mydb --dir ./connector --hub-connector hasura/postgres
# Initialize a NodeJS Connector "mylambda" in the Subgraph "app" on port 8765
ddn connector init mylambda --subgraph ./app/subgraph.yaml --hub-connector hasura/nodejs --configure-port 8765
Options
--add-to-compose-file string The compose file to include the generated connector compose file
--ci Disables the use of context
--configure-port string Initialise the connector with an already configured port
-c, --context string Name of the context to use. (default <current_context>)
--dir string Directory to initialize the Connector
-h, --help help for init
--hub-connector string Name and version of Connector in Hasura Connector Hub. ref: https://hasura.io/connectors
-i, --interactive Interactive mode
--no-link Do not create a ConnectorLink
--subgraph string Subgraph to initialize the Connector in
--target-env-file string Path to the environment 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 connector - Perform Connector related operations