@superglue/cli 1.1.213 → 1.1.215

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -44,7 +44,7 @@ Read these on demand — they are authoritative for their topic and kept in sync
44
44
 
45
45
  **Authentication & Credentials**
46
46
 
47
- - `sg system call --system-id <id> --url <url>` selects your credential (your starred one, otherwise the accessible one you have held longest, owned or shared), refreshes OAuth tokens, and adds the `Authorization` header for `oauth2`, `basic_auth`, and `api_key` systems. The output reports `credential` and `auth`; `auth.applied: "unavailable"` names what is missing. Pass `--credential-id` to use a specific credential. `--url` is the absolute URL, or `<<systemId_url>>` plus the path for tenant-specific hosts.
47
+ - `sg system call --system-id <id> --url <url>` selects your connection (your starred one, otherwise the accessible one you have held longest, owned or shared), refreshes OAuth tokens, and adds the `Authorization` header for `oauth2`, `basic_auth`, and `api_key` systems. The output reports the connection as `credential`, plus `auth`; `auth.applied: "unavailable"` names what is missing. Pass `--connection-id` to use a specific connection. `--url` is the absolute URL, or `<<systemId_url>>` plus the path for tenant-specific hosts.
48
48
  - Pass `--headers` with `<<systemId_credentialKey>>` placeholders only when the API expects another header or a query parameter; that replaces the default header. `sg system find --id <id>` prints each secret's exact placeholder; `sg system call` rejects bare `<<credentialKey>>` placeholders before sending.
49
49
  - Saved tool steps inject nothing: put the auth header or connection string in the step config.
50
50
  - Databases/Redis/file servers: embed credential placeholders in the connection URL (e.g. `postgres://<<sys_user>>:<<sys_pass>>@host/db`).
@@ -253,7 +253,7 @@ Agents familiar with the web agent (its native tools and the `superglue` node mo
253
253
  | `run_command` with `vfs` for `/org/connections/` | `sg system find <query>` / `--id <id>` | Returns your connection's secret names, url, and auth type |
254
254
  | `/org/connections/<id>.json` | `sg system connection list/get/set/clear` | Manage your connection; `--connection-id` targets a specific one |
255
255
  | `tools.callSystem` | `sg system call --system-id <id> --url <url>` | Ad-hoc calls; connection and auth header are added server-side; `--connection-id` matches `credentialId` |
256
- | `create_connection` | `sg system connection set` and `sg system oauth` | Saves configuration and secrets, then opens OAuth when needed |
256
+ | `connect` | `sg system connection set` and `sg system oauth` | Saves configuration and secrets, then opens OAuth when needed |
257
257
  | `run_command` with `vfs` for `/org/runs/` | `sg run list` / `sg run get <runId>` | Filter `list` by `--tool`, `--status`, `--source`, `--limit` |
258
258
  | `run_command` with `vfs` for `/org/mcp-servers/` | `sg mcp list` / `sg mcp find --id <id>` | Returns endpoint, auth mode, selected tool IDs, and client config |
259
259
  | `tools.writeMcpServer` (superglue module; new) | `sg mcp create --name <n> --tool <id>` | Creates a named MCP endpoint for selected saved tools |
@@ -266,7 +266,7 @@ Agents familiar with the web agent (its native tools and the `superglue` node mo
266
266
  | `tools.writeProjectLabel` (superglue module) | `sg project label create` / `label edit` | Same fields; `sg project label delete` has no module equivalent |
267
267
  | (no direct equivalent) | `sg login`, `sg update`, `sg skill` | CLI-specific setup, updater, and this reference system |
268
268
 
269
- Web-agent-only concepts with no CLI equivalent: `run_command`'s virtual filesystem (CLI uses concrete `sg` subcommands), `create_connection`'s secure input form (CLI accepts secrets through connection commands), and `setup_gateway` (the gateway install command is created in the web app).
269
+ Web-agent-only concepts with no CLI equivalent: `run_command`'s virtual filesystem (CLI uses concrete `sg` subcommands), `connect`'s secure input form (CLI accepts secrets through connection commands), and `setup_gateway` (the gateway install command is created in the web app).
270
270
 
271
271
  ### Command Reference
272
272
 
@@ -31,6 +31,7 @@ Constraints:
31
31
 
32
32
  - Bare `file::<key>` without a suffix is invalid and causes a runtime error
33
33
  - File references resolve only in body/content fields, not in headers, query params, or URLs
34
+ - `.raw` must be the whole field value; embedding it inside a string fails. `.base64` and `.extracted` can appear inside strings
34
35
  - Multi-file steps use bracket notation: `file::stepId["report.csv"].raw`
35
36
  - Loop iterations use numeric index: `file::stepId[0].raw`
36
37
 
@@ -65,9 +65,9 @@ sftp://<<my_server_username>>:<<my_server_password>>@host/path
65
65
 
66
66
  **SFTP private key auth:** store `privateKey` and `passphrase` as secrets on the connection instead of URL password placeholders.
67
67
 
68
- **SMB domain auth:** use `domain\user` format in the URL, or store `domain` as a system credential.
68
+ **SMB domain auth:** use `domain\user` format in the URL, or store `domain` as a connection secret.
69
69
 
70
- Store these secrets on the connection: `host`, `port`, `username`, `password`, `privateKey`, `passphrase`, `domain` (SMB), `home_dir`. Paths and share names belong in the URL, not in credentials.
70
+ Secrets on the connection (`--credentials`): `username`, `password`, `privateKey`, `passphrase`, `domain` (SMB). `host`, `port`, `path`, and `homeDirectory` belong in the URL or in `--authentication` `config` with type `connection_string`, never in secrets.
71
71
 
72
72
  ## File Server Runtime Details
73
73
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@superglue/cli",
3
- "version": "1.1.213",
3
+ "version": "1.1.215",
4
4
  "bin": {
5
5
  "sg": "./dist/cli.js"
6
6
  },
@@ -44,7 +44,7 @@ Read these on demand — they are authoritative for their topic and kept in sync
44
44
 
45
45
  **Authentication & Credentials**
46
46
 
47
- - `sg system call --system-id <id> --url <url>` selects your credential (your starred one, otherwise the accessible one you have held longest, owned or shared), refreshes OAuth tokens, and adds the `Authorization` header for `oauth2`, `basic_auth`, and `api_key` systems. The output reports `credential` and `auth`; `auth.applied: "unavailable"` names what is missing. Pass `--credential-id` to use a specific credential. `--url` is the absolute URL, or `<<systemId_url>>` plus the path for tenant-specific hosts.
47
+ - `sg system call --system-id <id> --url <url>` selects your connection (your starred one, otherwise the accessible one you have held longest, owned or shared), refreshes OAuth tokens, and adds the `Authorization` header for `oauth2`, `basic_auth`, and `api_key` systems. The output reports the connection as `credential`, plus `auth`; `auth.applied: "unavailable"` names what is missing. Pass `--connection-id` to use a specific connection. `--url` is the absolute URL, or `<<systemId_url>>` plus the path for tenant-specific hosts.
48
48
  - Pass `--headers` with `<<systemId_credentialKey>>` placeholders only when the API expects another header or a query parameter; that replaces the default header. `sg system find --id <id>` prints each secret's exact placeholder; `sg system call` rejects bare `<<credentialKey>>` placeholders before sending.
49
49
  - Saved tool steps inject nothing: put the auth header or connection string in the step config.
50
50
  - Databases/Redis/file servers: embed credential placeholders in the connection URL (e.g. `postgres://<<sys_user>>:<<sys_pass>>@host/db`).
@@ -253,7 +253,7 @@ Agents familiar with the web agent (its native tools and the `superglue` node mo
253
253
  | `run_command` with `vfs` for `/org/connections/` | `sg system find <query>` / `--id <id>` | Returns your connection's secret names, url, and auth type |
254
254
  | `/org/connections/<id>.json` | `sg system connection list/get/set/clear` | Manage your connection; `--connection-id` targets a specific one |
255
255
  | `tools.callSystem` | `sg system call --system-id <id> --url <url>` | Ad-hoc calls; connection and auth header are added server-side; `--connection-id` matches `credentialId` |
256
- | `create_connection` | `sg system connection set` and `sg system oauth` | Saves configuration and secrets, then opens OAuth when needed |
256
+ | `connect` | `sg system connection set` and `sg system oauth` | Saves configuration and secrets, then opens OAuth when needed |
257
257
  | `run_command` with `vfs` for `/org/runs/` | `sg run list` / `sg run get <runId>` | Filter `list` by `--tool`, `--status`, `--source`, `--limit` |
258
258
  | `run_command` with `vfs` for `/org/mcp-servers/` | `sg mcp list` / `sg mcp find --id <id>` | Returns endpoint, auth mode, selected tool IDs, and client config |
259
259
  | `tools.writeMcpServer` (superglue module; new) | `sg mcp create --name <n> --tool <id>` | Creates a named MCP endpoint for selected saved tools |
@@ -266,7 +266,7 @@ Agents familiar with the web agent (its native tools and the `superglue` node mo
266
266
  | `tools.writeProjectLabel` (superglue module) | `sg project label create` / `label edit` | Same fields; `sg project label delete` has no module equivalent |
267
267
  | (no direct equivalent) | `sg login`, `sg update`, `sg skill` | CLI-specific setup, updater, and this reference system |
268
268
 
269
- Web-agent-only concepts with no CLI equivalent: `run_command`'s virtual filesystem (CLI uses concrete `sg` subcommands), `create_connection`'s secure input form (CLI accepts secrets through connection commands), and `setup_gateway` (the gateway install command is created in the web app).
269
+ Web-agent-only concepts with no CLI equivalent: `run_command`'s virtual filesystem (CLI uses concrete `sg` subcommands), `connect`'s secure input form (CLI accepts secrets through connection commands), and `setup_gateway` (the gateway install command is created in the web app).
270
270
 
271
271
  ### Command Reference
272
272
 
@@ -31,6 +31,7 @@ Constraints:
31
31
 
32
32
  - Bare `file::<key>` without a suffix is invalid and causes a runtime error
33
33
  - File references resolve only in body/content fields, not in headers, query params, or URLs
34
+ - `.raw` must be the whole field value; embedding it inside a string fails. `.base64` and `.extracted` can appear inside strings
34
35
  - Multi-file steps use bracket notation: `file::stepId["report.csv"].raw`
35
36
  - Loop iterations use numeric index: `file::stepId[0].raw`
36
37
 
@@ -65,9 +65,9 @@ sftp://<<my_server_username>>:<<my_server_password>>@host/path
65
65
 
66
66
  **SFTP private key auth:** store `privateKey` and `passphrase` as secrets on the connection instead of URL password placeholders.
67
67
 
68
- **SMB domain auth:** use `domain\user` format in the URL, or store `domain` as a system credential.
68
+ **SMB domain auth:** use `domain\user` format in the URL, or store `domain` as a connection secret.
69
69
 
70
- Store these secrets on the connection: `host`, `port`, `username`, `password`, `privateKey`, `passphrase`, `domain` (SMB), `home_dir`. Paths and share names belong in the URL, not in credentials.
70
+ Secrets on the connection (`--credentials`): `username`, `password`, `privateKey`, `passphrase`, `domain` (SMB). `host`, `port`, `path`, and `homeDirectory` belong in the URL or in `--authentication` `config` with type `connection_string`, never in secrets.
71
71
 
72
72
  ## File Server Runtime Details
73
73