Lists the connectors with their domain, auth type and scopes, and the Overlane-native feature each one complements. Connectors are optional on every plan: the native suite works with none connected. Show one in full with overlane connector show \<provider\>.
Usage
overlane connector list [--service URL] [--team TENANT_ID]Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--service |
string | no | The service address (default: OVERLANE_SERVICE_URL, then the project’s binding, then the hosted service) | |
--team |
string | no | The team (tenant) to act on (default: the one your token belongs to) |
Examples
overlane connector list
overlane connector list --jsonBehavior
- Effect:
read(changes nothing). - Needs credentials: yes. Uses the network: yes.
- Supports
--dry-run: no. Accepts--force: no. - Machine-readable description:
overlane schema connector list.
Result
With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.
{
"type": "object",
"properties": {
"tenantId": {
"type": "string"
},
"connectors": {
"type": "array",
"items": {
"type": "object",
"properties": {
"provider": {
"type": "string"
},
"name": {
"type": "string"
},
"domain": {
"type": "string"
},
"auth": {
"type": "string"
},
"actions": {
"type": "number"
},
"nativeAlternative": {
"type": "string"
}
},
"required": [
"provider",
"name",
"domain",
"auth",
"actions",
"nativeAlternative"
],
"additionalProperties": false
}
},
"next": {
"type": "string"
}
},
"required": [
"tenantId",
"connectors",
"next"
],
"additionalProperties": false
}See exit codes for the status the process returns.