@superglue/cli 1.1.270 → 1.1.272

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.
@@ -587,6 +587,8 @@ Basic auth auto-encodes: if the value after `Basic ` isn't already base64, the e
587
587
 
588
588
  **Credential lifecycle:**
589
589
 
590
+ OAuth saves provider metadata from both the callback and token response automatically, including company IDs and instance URLs. Ordinary field names become connection secrets, such as `realmId` or `instance_url`; use their `<<systemId_secretName>>` placeholders before asking the user for these values. The `oauth_metadata` secret holds the metadata as JSON under `callback` and `tokenResponse`, including nested fields and names that cannot be secret names. For example, `<<(data) => JSON.parse(data.my_api_oauth_metadata).tokenResponse.team.id>>` reads a nested team ID. Refresh preserves omitted metadata and updates fields the provider returns. Callback data cannot replace OAuth tokens or client configuration.
591
+
590
592
  - Pass all secret values via `--credentials '{"api_key":"...","client_secret":"..."}'` on create/edit
591
593
  - Use `sg system connection set --system-id <id> --credentials '{...}'` to save secrets on the current API-key user's connection
592
594
  - Use `sg system connection get --system-id <id>` to inspect the current user's secret names and whether each has a non-empty value; secret values are never returned
@@ -34,7 +34,7 @@ For APIs that require the same query key multiple times, use an array value:
34
34
 
35
35
  ## Authentication
36
36
 
37
- Saved tool steps never inject credentials: place auth headers explicitly with `<<systemId_credentialKey>>` placeholders. `sg system call` adds the `Authorization` header itself for `oauth2` (Bearer), `basic_auth` (Basic), and `api_key` (Bearer) systems; pass your own header only when the API expects a different one.
37
+ Saved tool steps never inject credentials: place auth headers explicitly with `<<systemId_credentialKey>>` placeholders.
38
38
 
39
39
  ```javascript
40
40
  // Bearer token (including OAuth — token refresh is automatic, the step header is not)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@superglue/cli",
3
- "version": "1.1.270",
3
+ "version": "1.1.272",
4
4
  "bin": {
5
5
  "sg": "./dist/cli.js"
6
6
  },
@@ -587,6 +587,8 @@ Basic auth auto-encodes: if the value after `Basic ` isn't already base64, the e
587
587
 
588
588
  **Credential lifecycle:**
589
589
 
590
+ OAuth saves provider metadata from both the callback and token response automatically, including company IDs and instance URLs. Ordinary field names become connection secrets, such as `realmId` or `instance_url`; use their `<<systemId_secretName>>` placeholders before asking the user for these values. The `oauth_metadata` secret holds the metadata as JSON under `callback` and `tokenResponse`, including nested fields and names that cannot be secret names. For example, `<<(data) => JSON.parse(data.my_api_oauth_metadata).tokenResponse.team.id>>` reads a nested team ID. Refresh preserves omitted metadata and updates fields the provider returns. Callback data cannot replace OAuth tokens or client configuration.
591
+
590
592
  - Pass all secret values via `--credentials '{"api_key":"...","client_secret":"..."}'` on create/edit
591
593
  - Use `sg system connection set --system-id <id> --credentials '{...}'` to save secrets on the current API-key user's connection
592
594
  - Use `sg system connection get --system-id <id>` to inspect the current user's secret names and whether each has a non-empty value; secret values are never returned
@@ -34,7 +34,7 @@ For APIs that require the same query key multiple times, use an array value:
34
34
 
35
35
  ## Authentication
36
36
 
37
- Saved tool steps never inject credentials: place auth headers explicitly with `<<systemId_credentialKey>>` placeholders. `sg system call` adds the `Authorization` header itself for `oauth2` (Bearer), `basic_auth` (Basic), and `api_key` (Bearer) systems; pass your own header only when the API expects a different one.
37
+ Saved tool steps never inject credentials: place auth headers explicitly with `<<systemId_credentialKey>>` placeholders.
38
38
 
39
39
  ```javascript
40
40
  // Bearer token (including OAuth — token refresh is automatic, the step header is not)