@superglue/cli 1.1.93 → 1.1.95
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
|
**Authentication & Credentials**
|
|
45
45
|
|
|
46
46
|
- Authentication must ALWAYS be explicitly configured — nothing is injected automatically in any protocol.
|
|
47
|
-
- HTTP: include auth headers using `<<systemId_credentialKey>>` (e.g. `"Authorization": "Bearer <<my_api_access_token>>"`).
|
|
47
|
+
- HTTP: include auth headers using `<<systemId_credentialKey>>` (e.g. `"Authorization": "Bearer <<my_api_access_token>>"`). `sg system find --id <id>` prints each secret's exact placeholder; `sg system call` rejects bare `<<credentialKey>>` placeholders before sending.
|
|
48
48
|
- Databases/Redis/file servers: embed credential placeholders in the connection URL (e.g. `postgres://<<sys_user>>:<<sys_pass>>@host/db`).
|
|
49
49
|
- OAuth: token refresh is automatic, but the header must still be explicit.
|
|
50
50
|
|
|
@@ -87,6 +87,15 @@ XML responses (SOAP and other XML APIs) are auto-parsed to an object on `sourceD
|
|
|
87
87
|
- Default headers: `Accept: */*`, Chrome-like `User-Agent`
|
|
88
88
|
- HTTPS: `rejectUnauthorized: false` (accepts self-signed certs)
|
|
89
89
|
|
|
90
|
+
### Tool Step Response Metadata
|
|
91
|
+
|
|
92
|
+
Set `config.captureHttpResponse: true` on HTTP request steps that need response metadata. The default is off.
|
|
93
|
+
Successful steps expose `sourceData.stepId.http.statusCode` and `sourceData.stepId.http.headers`; `.data` remains the response body.
|
|
94
|
+
Loop results carry `.http` per item. Pagination exposes the final response's metadata; stop conditions retain per-page `response.headers`.
|
|
95
|
+
Stored `stepResults` retain the metadata, including failed HTTP responses. No HTTP response means no `.http` field.
|
|
96
|
+
Header names are lowercase; `set-cookie` values are arrays, and other values are strings.
|
|
97
|
+
Steps without the option keep their existing envelopes and outputs.
|
|
98
|
+
|
|
90
99
|
### Body Resolution
|
|
91
100
|
|
|
92
101
|
The runtime processes the body in this order:
|
package/package.json
CHANGED
|
@@ -44,7 +44,7 @@ Read these on demand — they are authoritative for their topic and kept in sync
|
|
|
44
44
|
**Authentication & Credentials**
|
|
45
45
|
|
|
46
46
|
- Authentication must ALWAYS be explicitly configured — nothing is injected automatically in any protocol.
|
|
47
|
-
- HTTP: include auth headers using `<<systemId_credentialKey>>` (e.g. `"Authorization": "Bearer <<my_api_access_token>>"`).
|
|
47
|
+
- HTTP: include auth headers using `<<systemId_credentialKey>>` (e.g. `"Authorization": "Bearer <<my_api_access_token>>"`). `sg system find --id <id>` prints each secret's exact placeholder; `sg system call` rejects bare `<<credentialKey>>` placeholders before sending.
|
|
48
48
|
- Databases/Redis/file servers: embed credential placeholders in the connection URL (e.g. `postgres://<<sys_user>>:<<sys_pass>>@host/db`).
|
|
49
49
|
- OAuth: token refresh is automatic, but the header must still be explicit.
|
|
50
50
|
|
|
@@ -87,6 +87,15 @@ XML responses (SOAP and other XML APIs) are auto-parsed to an object on `sourceD
|
|
|
87
87
|
- Default headers: `Accept: */*`, Chrome-like `User-Agent`
|
|
88
88
|
- HTTPS: `rejectUnauthorized: false` (accepts self-signed certs)
|
|
89
89
|
|
|
90
|
+
### Tool Step Response Metadata
|
|
91
|
+
|
|
92
|
+
Set `config.captureHttpResponse: true` on HTTP request steps that need response metadata. The default is off.
|
|
93
|
+
Successful steps expose `sourceData.stepId.http.statusCode` and `sourceData.stepId.http.headers`; `.data` remains the response body.
|
|
94
|
+
Loop results carry `.http` per item. Pagination exposes the final response's metadata; stop conditions retain per-page `response.headers`.
|
|
95
|
+
Stored `stepResults` retain the metadata, including failed HTTP responses. No HTTP response means no `.http` field.
|
|
96
|
+
Header names are lowercase; `set-cookie` values are arrays, and other values are strings.
|
|
97
|
+
Steps without the option keep their existing envelopes and outputs.
|
|
98
|
+
|
|
90
99
|
### Body Resolution
|
|
91
100
|
|
|
92
101
|
The runtime processes the body in this order:
|