@soat/sdk 0.96.0 → 0.97.0
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.
- package/dist/index.cjs +1 -1
- package/dist/index.d.cts +17 -11
- package/dist/index.d.mts +17 -11
- package/dist/index.mjs +1 -1
- package/package.json +1 -1
package/dist/index.cjs
CHANGED
|
@@ -4681,7 +4681,7 @@ var Shares = class {
|
|
|
4681
4681
|
/**
|
|
4682
4682
|
* List a grantee's references to a shared resource
|
|
4683
4683
|
*
|
|
4684
|
-
* The grantee project's own resources
|
|
4684
|
+
* The grantee project's own resources a run reaches the resource the share grants from: those naming it (agents binding a shared tool, pipelines stepping through it, ingestion rules converting with it, orchestrations, playbooks, triggers and formations naming it) and, transitively, those naming one of them (deciders and evals on such an agent, workflows dispatching it, triggers firing such an orchestration). Each is listed once, grouped by `type` in the enum's order. What degrades if the project revokes its acceptance, and what `409 SHARE_IN_USE` lists. The grantee is named by `project_id` or by its scoped credential; the publisher holds none of these and is answered `400`.
|
|
4685
4685
|
*/
|
|
4686
4686
|
static listShareReferences(options) {
|
|
4687
4687
|
return (options.client ?? client).get({
|
package/dist/index.d.cts
CHANGED
|
@@ -5605,7 +5605,7 @@ type OrchestrationNode = {
|
|
|
5605
5605
|
[key: string]: unknown;
|
|
5606
5606
|
};
|
|
5607
5607
|
/**
|
|
5608
|
-
* Maps state write paths to values. Each key is a `state.<path>` destination (the `state.` prefix is optional); each value is JSON Logic (https://jsonlogic.com) evaluated against `{ "output": <node artifact>, "state": <run state> }` — e.g. `{ "summary": {"var": "output.content"} }` writes the artifact's `content` field to `state.summary`. The same evaluator as input_mapping/transform/condition; only the context differs. An `agent` node's artifact always carries both `content` (the text response) and `object` (the parsed value when a schema applied, `null` otherwise), so `output.content` reads the same whether or not the node declares an `output_schema`.
|
|
5608
|
+
* Maps state write paths to values. Each key is a `state.<path>` destination (the `state.` prefix is optional); each value is JSON Logic (https://jsonlogic.com) evaluated against `{ "output": <node artifact>, "state": <run state> }` — e.g. `{ "summary": {"var": "output.content"} }` writes the artifact's `content` field to `state.summary`. The same evaluator as input_mapping/transform/condition; only the context differs. No key segment may be `__proto__`, `constructor` or `prototype`. An `agent` node's artifact always carries both `content` (the text response) and `object` (the parsed value when a schema applied, `null` otherwise), so `output.content` reads the same whether or not the node declares an `output_schema`.
|
|
5609
5609
|
*
|
|
5610
5610
|
*/
|
|
5611
5611
|
state_mapping?: {
|
|
@@ -5767,7 +5767,7 @@ type Orchestration = {
|
|
|
5767
5767
|
updated_at: Date;
|
|
5768
5768
|
};
|
|
5769
5769
|
/**
|
|
5770
|
-
* The shape of a completed run's `output`, owned by the orchestration rather than by its terminal node ids. Each key is an output field (a dotted key such as `summary.title` builds a nested object); each value is JSON Logic (https://jsonlogic.com) evaluated against `{ "state": <final run state> }`, which includes `state.input` and `state.nodes.<id>`. A missing path maps to `null`; a mapping that throws fails the run. Null (or omitted) keys `output` by terminal node id. Versioned with the graph; `null` on update clears it.
|
|
5770
|
+
* The shape of a completed run's `output`, owned by the orchestration rather than by its terminal node ids. Each key is an output field (a dotted key such as `summary.title` builds a nested object, and no segment may be `__proto__`, `constructor` or `prototype`); each value is JSON Logic (https://jsonlogic.com) evaluated against `{ "state": <final run state> }`, which includes `state.input` and `state.nodes.<id>`. A missing path maps to `null`; a mapping that throws fails the run. Null (or omitted) keys `output` by terminal node id. Versioned with the graph; `null` on update clears it.
|
|
5771
5771
|
*/
|
|
5772
5772
|
type OrchestrationOutputMapping = {
|
|
5773
5773
|
[key: string]: unknown;
|
|
@@ -7255,13 +7255,13 @@ type ShareCap = {
|
|
|
7255
7255
|
window: 'rolling_1m' | 'rolling_1h' | 'rolling_24h' | 'calendar_month';
|
|
7256
7256
|
};
|
|
7257
7257
|
/**
|
|
7258
|
-
* One of the grantee project's resources
|
|
7258
|
+
* One of the grantee project's resources a run reaches the shared resource from.
|
|
7259
7259
|
*/
|
|
7260
7260
|
type ShareReference = {
|
|
7261
7261
|
/**
|
|
7262
7262
|
* The kind of the grantee's resource.
|
|
7263
7263
|
*/
|
|
7264
|
-
type: 'agent' | 'tool' | 'ingestion_rule' | 'orchestration' | 'trigger' | 'formation';
|
|
7264
|
+
type: 'agent' | 'tool' | 'decider' | 'ingestion_rule' | 'orchestration' | 'workflow' | 'playbook' | 'eval' | 'trigger' | 'formation';
|
|
7265
7265
|
/**
|
|
7266
7266
|
* Its public ID.
|
|
7267
7267
|
*/
|
|
@@ -7571,7 +7571,7 @@ type Tool = {
|
|
|
7571
7571
|
[key: string]: unknown;
|
|
7572
7572
|
} | null;
|
|
7573
7573
|
/**
|
|
7574
|
-
* Execution config for http tools. Supported fields: `url` (required), `method` (default `POST`), `headers`, `body_mode` and `response_mode`. The `url` may contain `{paramName}` placeholders (e.g. `/users/{userId}`) that are replaced at call time with the corresponding tool argument value (URL-encoded). Arguments consumed as path parameters are excluded from the query string and request body. `body_mode` is `json` (default) or `multipart`. In `multipart` mode the merged tool arguments are sent as a `multipart/form-data` body: scalar fields become plain form fields and a field shaped like `{ content_type, filename, data_base64 }` is decoded from base64 and attached as a file part (the hardcoded `Content-Type: application/json` is dropped so `fetch` sets the multipart boundary itself). `response_mode` is `json` (default: the body parsed as JSON, else returned as text) or `base64`, which returns a 2xx body as `{ content_type, filename, data_base64 }` — the same file shape `multipart` accepts, so a pipeline step can relay a downloaded file. `filename` comes from `Content-Disposition` and is omitted when the target names none
|
|
7574
|
+
* Execution config for http tools. Supported fields: `url` (required), `method` (default `POST`), `headers`, `body_mode` and `response_mode`. The `url` may contain `{paramName}` placeholders (e.g. `/users/{userId}`) that are replaced at call time with the corresponding tool argument value (URL-encoded). Arguments consumed as path parameters are excluded from the query string and request body. `body_mode` is `json` (default) or `multipart`. In `multipart` mode the merged tool arguments are sent as a `multipart/form-data` body: scalar fields become plain form fields and a field shaped like `{ content_type, filename, data_base64 }` is decoded from base64 and attached as a file part (the hardcoded `Content-Type: application/json` is dropped so `fetch` sets the multipart boundary itself). `response_mode` is `json` (default: the body parsed as JSON, else returned as text) or `base64`, which returns a 2xx body as `{ content_type, filename, data_base64 }` — the same file shape `multipart` accepts, so a pipeline step can relay a downloaded file. `filename` comes from `Content-Disposition` and is omitted when the target names none. In either mode a 2xx body over `TOOL_RESPONSE_MAX_BYTES` is `502 TOOL_RESPONSE_TOO_LARGE`; a non-2xx body over it is cut to it.
|
|
7575
7575
|
*
|
|
7576
7576
|
* `auth` adds a computed request credential, for targets whose `Authorization` value cannot be expressed as a static header. Supported `auth.type` values:
|
|
7577
7577
|
*
|
|
@@ -7764,7 +7764,7 @@ type CallToolRequest = {
|
|
|
7764
7764
|
};
|
|
7765
7765
|
};
|
|
7766
7766
|
/**
|
|
7767
|
-
* Execution config for http tools. An `http` tool without a non-empty `url` is `400 VALIDATION_FAILED`, on create and on an update that would leave it without one. Supported fields: `url` (required), `method` (default `POST`), `headers`, `body_mode` and `response_mode`. The `url` may contain `{paramName}` placeholders (e.g. `/users/{userId}`) that are replaced at call time with the corresponding tool argument value (URL-encoded). Arguments consumed as path parameters are excluded from the query string and request body. `body_mode` is `json` (default) or `multipart`. In `multipart` mode the merged tool arguments are sent as a `multipart/form-data` body: scalar fields become plain form fields and a field shaped like `{ content_type, filename, data_base64 }` is decoded from base64 and attached as a file part (the hardcoded `Content-Type: application/json` is dropped so `fetch` sets the multipart boundary itself). `response_mode` is `json` (default: the body parsed as JSON, else returned as text) or `base64`, which returns a 2xx body as `{ content_type, filename, data_base64 }` — the same file shape `multipart` accepts, so a pipeline step can relay a downloaded file. `filename` comes from `Content-Disposition` and is omitted when the target names none
|
|
7767
|
+
* Execution config for http tools. An `http` tool without a non-empty `url` is `400 VALIDATION_FAILED`, on create and on an update that would leave it without one. Supported fields: `url` (required), `method` (default `POST`), `headers`, `body_mode` and `response_mode`. The `url` may contain `{paramName}` placeholders (e.g. `/users/{userId}`) that are replaced at call time with the corresponding tool argument value (URL-encoded). Arguments consumed as path parameters are excluded from the query string and request body. `body_mode` is `json` (default) or `multipart`. In `multipart` mode the merged tool arguments are sent as a `multipart/form-data` body: scalar fields become plain form fields and a field shaped like `{ content_type, filename, data_base64 }` is decoded from base64 and attached as a file part (the hardcoded `Content-Type: application/json` is dropped so `fetch` sets the multipart boundary itself). `response_mode` is `json` (default: the body parsed as JSON, else returned as text) or `base64`, which returns a 2xx body as `{ content_type, filename, data_base64 }` — the same file shape `multipart` accepts, so a pipeline step can relay a downloaded file. `filename` comes from `Content-Disposition` and is omitted when the target names none. In either mode a 2xx body over `TOOL_RESPONSE_MAX_BYTES` is `502 TOOL_RESPONSE_TOO_LARGE`; a non-2xx body over it is cut to it.
|
|
7768
7768
|
*
|
|
7769
7769
|
* `auth` adds a computed request credential, for targets whose `Authorization` value cannot be expressed as a static header. Supported `auth.type` values:
|
|
7770
7770
|
*
|
|
@@ -8093,7 +8093,7 @@ type TriggerFiring = {
|
|
|
8093
8093
|
*/
|
|
8094
8094
|
error?: StoredError | null;
|
|
8095
8095
|
/**
|
|
8096
|
-
* `<event_id>:<trigger_id>` for an `event` firing, where `event_id` is the `id` in `input`;
|
|
8096
|
+
* `<event_id>:<trigger_id>` for an `event` firing, where `event_id` is the `id` in `input`; `<v1>:<trigger_id>` for a `webhook` firing whose delivery carried the timestamped `t=,v1=` signature; null otherwise. The same event reaching the same trigger twice produces one firing under this key, so a consumer reading firings can recognise a redelivery; a replayed signed delivery is refused.
|
|
8097
8097
|
*/
|
|
8098
8098
|
idempotency_key?: string | null;
|
|
8099
8099
|
/**
|
|
@@ -10527,7 +10527,7 @@ type ListAiProvidersResponses = {
|
|
|
10527
10527
|
*/
|
|
10528
10528
|
base_url?: string;
|
|
10529
10529
|
/**
|
|
10530
|
-
* Additional provider-specific configuration. Absent when the record sets none.
|
|
10530
|
+
* Additional provider-specific configuration. Absent when the record sets none. A `config.apiKey` reads as `{"no_echo": true}`.
|
|
10531
10531
|
*/
|
|
10532
10532
|
config?: {
|
|
10533
10533
|
[key: string]: unknown;
|
|
@@ -10566,7 +10566,7 @@ type CreateAiProviderData = {
|
|
|
10566
10566
|
*/
|
|
10567
10567
|
base_url?: string;
|
|
10568
10568
|
/**
|
|
10569
|
-
* Additional provider-specific configuration
|
|
10569
|
+
* Additional provider-specific configuration. `config.apiKey`, when set, must be a string; every read returns it as `{"no_echo": true}`.
|
|
10570
10570
|
*/
|
|
10571
10571
|
config?: {
|
|
10572
10572
|
[key: string]: unknown;
|
|
@@ -10724,6 +10724,9 @@ type GetAiProviderResponses = {
|
|
|
10724
10724
|
project_id?: string;
|
|
10725
10725
|
secret_id?: string | null;
|
|
10726
10726
|
base_url?: string;
|
|
10727
|
+
/**
|
|
10728
|
+
* Additional provider-specific configuration. A `config.apiKey` reads as `{"no_echo": true}`.
|
|
10729
|
+
*/
|
|
10727
10730
|
config?: {
|
|
10728
10731
|
[key: string]: unknown;
|
|
10729
10732
|
};
|
|
@@ -10742,6 +10745,9 @@ type UpdateAiProviderData = {
|
|
|
10742
10745
|
default_model?: string;
|
|
10743
10746
|
secret_id?: string | null;
|
|
10744
10747
|
base_url?: string;
|
|
10748
|
+
/**
|
|
10749
|
+
* Replaces the whole configuration, so a `config.apiKey` the record keeps is sent again as a string; the masked `{"no_echo": true}` a read returns is refused.
|
|
10750
|
+
*/
|
|
10745
10751
|
config?: {
|
|
10746
10752
|
[key: string]: unknown;
|
|
10747
10753
|
};
|
|
@@ -25069,7 +25075,7 @@ type RevokeShareErrors = {
|
|
|
25069
25075
|
*/
|
|
25070
25076
|
404: ErrorResponse;
|
|
25071
25077
|
/**
|
|
25072
|
-
* `SHARE_IN_USE`: the grantee's resources still
|
|
25078
|
+
* `SHARE_IN_USE`: the grantee's resources still reach the shared resource. `error.meta.references` lists them.
|
|
25073
25079
|
*/
|
|
25074
25080
|
409: ErrorResponse;
|
|
25075
25081
|
/**
|
|
@@ -30742,7 +30748,7 @@ export declare class Shares {
|
|
|
30742
30748
|
/**
|
|
30743
30749
|
* List a grantee's references to a shared resource
|
|
30744
30750
|
*
|
|
30745
|
-
* The grantee project's own resources
|
|
30751
|
+
* The grantee project's own resources a run reaches the resource the share grants from: those naming it (agents binding a shared tool, pipelines stepping through it, ingestion rules converting with it, orchestrations, playbooks, triggers and formations naming it) and, transitively, those naming one of them (deciders and evals on such an agent, workflows dispatching it, triggers firing such an orchestration). Each is listed once, grouped by `type` in the enum's order. What degrades if the project revokes its acceptance, and what `409 SHARE_IN_USE` lists. The grantee is named by `project_id` or by its scoped credential; the publisher holds none of these and is answered `400`.
|
|
30746
30752
|
*/
|
|
30747
30753
|
static listShareReferences<ThrowOnError extends boolean = false>(options: Options<ListShareReferencesData, ThrowOnError>): RequestResult<ListShareReferencesResponses, ListShareReferencesErrors, ThrowOnError>;
|
|
30748
30754
|
/**
|
package/dist/index.d.mts
CHANGED
|
@@ -5605,7 +5605,7 @@ type OrchestrationNode = {
|
|
|
5605
5605
|
[key: string]: unknown;
|
|
5606
5606
|
};
|
|
5607
5607
|
/**
|
|
5608
|
-
* Maps state write paths to values. Each key is a `state.<path>` destination (the `state.` prefix is optional); each value is JSON Logic (https://jsonlogic.com) evaluated against `{ "output": <node artifact>, "state": <run state> }` — e.g. `{ "summary": {"var": "output.content"} }` writes the artifact's `content` field to `state.summary`. The same evaluator as input_mapping/transform/condition; only the context differs. An `agent` node's artifact always carries both `content` (the text response) and `object` (the parsed value when a schema applied, `null` otherwise), so `output.content` reads the same whether or not the node declares an `output_schema`.
|
|
5608
|
+
* Maps state write paths to values. Each key is a `state.<path>` destination (the `state.` prefix is optional); each value is JSON Logic (https://jsonlogic.com) evaluated against `{ "output": <node artifact>, "state": <run state> }` — e.g. `{ "summary": {"var": "output.content"} }` writes the artifact's `content` field to `state.summary`. The same evaluator as input_mapping/transform/condition; only the context differs. No key segment may be `__proto__`, `constructor` or `prototype`. An `agent` node's artifact always carries both `content` (the text response) and `object` (the parsed value when a schema applied, `null` otherwise), so `output.content` reads the same whether or not the node declares an `output_schema`.
|
|
5609
5609
|
*
|
|
5610
5610
|
*/
|
|
5611
5611
|
state_mapping?: {
|
|
@@ -5767,7 +5767,7 @@ type Orchestration = {
|
|
|
5767
5767
|
updated_at: Date;
|
|
5768
5768
|
};
|
|
5769
5769
|
/**
|
|
5770
|
-
* The shape of a completed run's `output`, owned by the orchestration rather than by its terminal node ids. Each key is an output field (a dotted key such as `summary.title` builds a nested object); each value is JSON Logic (https://jsonlogic.com) evaluated against `{ "state": <final run state> }`, which includes `state.input` and `state.nodes.<id>`. A missing path maps to `null`; a mapping that throws fails the run. Null (or omitted) keys `output` by terminal node id. Versioned with the graph; `null` on update clears it.
|
|
5770
|
+
* The shape of a completed run's `output`, owned by the orchestration rather than by its terminal node ids. Each key is an output field (a dotted key such as `summary.title` builds a nested object, and no segment may be `__proto__`, `constructor` or `prototype`); each value is JSON Logic (https://jsonlogic.com) evaluated against `{ "state": <final run state> }`, which includes `state.input` and `state.nodes.<id>`. A missing path maps to `null`; a mapping that throws fails the run. Null (or omitted) keys `output` by terminal node id. Versioned with the graph; `null` on update clears it.
|
|
5771
5771
|
*/
|
|
5772
5772
|
type OrchestrationOutputMapping = {
|
|
5773
5773
|
[key: string]: unknown;
|
|
@@ -7255,13 +7255,13 @@ type ShareCap = {
|
|
|
7255
7255
|
window: 'rolling_1m' | 'rolling_1h' | 'rolling_24h' | 'calendar_month';
|
|
7256
7256
|
};
|
|
7257
7257
|
/**
|
|
7258
|
-
* One of the grantee project's resources
|
|
7258
|
+
* One of the grantee project's resources a run reaches the shared resource from.
|
|
7259
7259
|
*/
|
|
7260
7260
|
type ShareReference = {
|
|
7261
7261
|
/**
|
|
7262
7262
|
* The kind of the grantee's resource.
|
|
7263
7263
|
*/
|
|
7264
|
-
type: 'agent' | 'tool' | 'ingestion_rule' | 'orchestration' | 'trigger' | 'formation';
|
|
7264
|
+
type: 'agent' | 'tool' | 'decider' | 'ingestion_rule' | 'orchestration' | 'workflow' | 'playbook' | 'eval' | 'trigger' | 'formation';
|
|
7265
7265
|
/**
|
|
7266
7266
|
* Its public ID.
|
|
7267
7267
|
*/
|
|
@@ -7571,7 +7571,7 @@ type Tool = {
|
|
|
7571
7571
|
[key: string]: unknown;
|
|
7572
7572
|
} | null;
|
|
7573
7573
|
/**
|
|
7574
|
-
* Execution config for http tools. Supported fields: `url` (required), `method` (default `POST`), `headers`, `body_mode` and `response_mode`. The `url` may contain `{paramName}` placeholders (e.g. `/users/{userId}`) that are replaced at call time with the corresponding tool argument value (URL-encoded). Arguments consumed as path parameters are excluded from the query string and request body. `body_mode` is `json` (default) or `multipart`. In `multipart` mode the merged tool arguments are sent as a `multipart/form-data` body: scalar fields become plain form fields and a field shaped like `{ content_type, filename, data_base64 }` is decoded from base64 and attached as a file part (the hardcoded `Content-Type: application/json` is dropped so `fetch` sets the multipart boundary itself). `response_mode` is `json` (default: the body parsed as JSON, else returned as text) or `base64`, which returns a 2xx body as `{ content_type, filename, data_base64 }` — the same file shape `multipart` accepts, so a pipeline step can relay a downloaded file. `filename` comes from `Content-Disposition` and is omitted when the target names none
|
|
7574
|
+
* Execution config for http tools. Supported fields: `url` (required), `method` (default `POST`), `headers`, `body_mode` and `response_mode`. The `url` may contain `{paramName}` placeholders (e.g. `/users/{userId}`) that are replaced at call time with the corresponding tool argument value (URL-encoded). Arguments consumed as path parameters are excluded from the query string and request body. `body_mode` is `json` (default) or `multipart`. In `multipart` mode the merged tool arguments are sent as a `multipart/form-data` body: scalar fields become plain form fields and a field shaped like `{ content_type, filename, data_base64 }` is decoded from base64 and attached as a file part (the hardcoded `Content-Type: application/json` is dropped so `fetch` sets the multipart boundary itself). `response_mode` is `json` (default: the body parsed as JSON, else returned as text) or `base64`, which returns a 2xx body as `{ content_type, filename, data_base64 }` — the same file shape `multipart` accepts, so a pipeline step can relay a downloaded file. `filename` comes from `Content-Disposition` and is omitted when the target names none. In either mode a 2xx body over `TOOL_RESPONSE_MAX_BYTES` is `502 TOOL_RESPONSE_TOO_LARGE`; a non-2xx body over it is cut to it.
|
|
7575
7575
|
*
|
|
7576
7576
|
* `auth` adds a computed request credential, for targets whose `Authorization` value cannot be expressed as a static header. Supported `auth.type` values:
|
|
7577
7577
|
*
|
|
@@ -7764,7 +7764,7 @@ type CallToolRequest = {
|
|
|
7764
7764
|
};
|
|
7765
7765
|
};
|
|
7766
7766
|
/**
|
|
7767
|
-
* Execution config for http tools. An `http` tool without a non-empty `url` is `400 VALIDATION_FAILED`, on create and on an update that would leave it without one. Supported fields: `url` (required), `method` (default `POST`), `headers`, `body_mode` and `response_mode`. The `url` may contain `{paramName}` placeholders (e.g. `/users/{userId}`) that are replaced at call time with the corresponding tool argument value (URL-encoded). Arguments consumed as path parameters are excluded from the query string and request body. `body_mode` is `json` (default) or `multipart`. In `multipart` mode the merged tool arguments are sent as a `multipart/form-data` body: scalar fields become plain form fields and a field shaped like `{ content_type, filename, data_base64 }` is decoded from base64 and attached as a file part (the hardcoded `Content-Type: application/json` is dropped so `fetch` sets the multipart boundary itself). `response_mode` is `json` (default: the body parsed as JSON, else returned as text) or `base64`, which returns a 2xx body as `{ content_type, filename, data_base64 }` — the same file shape `multipart` accepts, so a pipeline step can relay a downloaded file. `filename` comes from `Content-Disposition` and is omitted when the target names none
|
|
7767
|
+
* Execution config for http tools. An `http` tool without a non-empty `url` is `400 VALIDATION_FAILED`, on create and on an update that would leave it without one. Supported fields: `url` (required), `method` (default `POST`), `headers`, `body_mode` and `response_mode`. The `url` may contain `{paramName}` placeholders (e.g. `/users/{userId}`) that are replaced at call time with the corresponding tool argument value (URL-encoded). Arguments consumed as path parameters are excluded from the query string and request body. `body_mode` is `json` (default) or `multipart`. In `multipart` mode the merged tool arguments are sent as a `multipart/form-data` body: scalar fields become plain form fields and a field shaped like `{ content_type, filename, data_base64 }` is decoded from base64 and attached as a file part (the hardcoded `Content-Type: application/json` is dropped so `fetch` sets the multipart boundary itself). `response_mode` is `json` (default: the body parsed as JSON, else returned as text) or `base64`, which returns a 2xx body as `{ content_type, filename, data_base64 }` — the same file shape `multipart` accepts, so a pipeline step can relay a downloaded file. `filename` comes from `Content-Disposition` and is omitted when the target names none. In either mode a 2xx body over `TOOL_RESPONSE_MAX_BYTES` is `502 TOOL_RESPONSE_TOO_LARGE`; a non-2xx body over it is cut to it.
|
|
7768
7768
|
*
|
|
7769
7769
|
* `auth` adds a computed request credential, for targets whose `Authorization` value cannot be expressed as a static header. Supported `auth.type` values:
|
|
7770
7770
|
*
|
|
@@ -8093,7 +8093,7 @@ type TriggerFiring = {
|
|
|
8093
8093
|
*/
|
|
8094
8094
|
error?: StoredError | null;
|
|
8095
8095
|
/**
|
|
8096
|
-
* `<event_id>:<trigger_id>` for an `event` firing, where `event_id` is the `id` in `input`;
|
|
8096
|
+
* `<event_id>:<trigger_id>` for an `event` firing, where `event_id` is the `id` in `input`; `<v1>:<trigger_id>` for a `webhook` firing whose delivery carried the timestamped `t=,v1=` signature; null otherwise. The same event reaching the same trigger twice produces one firing under this key, so a consumer reading firings can recognise a redelivery; a replayed signed delivery is refused.
|
|
8097
8097
|
*/
|
|
8098
8098
|
idempotency_key?: string | null;
|
|
8099
8099
|
/**
|
|
@@ -10527,7 +10527,7 @@ type ListAiProvidersResponses = {
|
|
|
10527
10527
|
*/
|
|
10528
10528
|
base_url?: string;
|
|
10529
10529
|
/**
|
|
10530
|
-
* Additional provider-specific configuration. Absent when the record sets none.
|
|
10530
|
+
* Additional provider-specific configuration. Absent when the record sets none. A `config.apiKey` reads as `{"no_echo": true}`.
|
|
10531
10531
|
*/
|
|
10532
10532
|
config?: {
|
|
10533
10533
|
[key: string]: unknown;
|
|
@@ -10566,7 +10566,7 @@ type CreateAiProviderData = {
|
|
|
10566
10566
|
*/
|
|
10567
10567
|
base_url?: string;
|
|
10568
10568
|
/**
|
|
10569
|
-
* Additional provider-specific configuration
|
|
10569
|
+
* Additional provider-specific configuration. `config.apiKey`, when set, must be a string; every read returns it as `{"no_echo": true}`.
|
|
10570
10570
|
*/
|
|
10571
10571
|
config?: {
|
|
10572
10572
|
[key: string]: unknown;
|
|
@@ -10724,6 +10724,9 @@ type GetAiProviderResponses = {
|
|
|
10724
10724
|
project_id?: string;
|
|
10725
10725
|
secret_id?: string | null;
|
|
10726
10726
|
base_url?: string;
|
|
10727
|
+
/**
|
|
10728
|
+
* Additional provider-specific configuration. A `config.apiKey` reads as `{"no_echo": true}`.
|
|
10729
|
+
*/
|
|
10727
10730
|
config?: {
|
|
10728
10731
|
[key: string]: unknown;
|
|
10729
10732
|
};
|
|
@@ -10742,6 +10745,9 @@ type UpdateAiProviderData = {
|
|
|
10742
10745
|
default_model?: string;
|
|
10743
10746
|
secret_id?: string | null;
|
|
10744
10747
|
base_url?: string;
|
|
10748
|
+
/**
|
|
10749
|
+
* Replaces the whole configuration, so a `config.apiKey` the record keeps is sent again as a string; the masked `{"no_echo": true}` a read returns is refused.
|
|
10750
|
+
*/
|
|
10745
10751
|
config?: {
|
|
10746
10752
|
[key: string]: unknown;
|
|
10747
10753
|
};
|
|
@@ -25069,7 +25075,7 @@ type RevokeShareErrors = {
|
|
|
25069
25075
|
*/
|
|
25070
25076
|
404: ErrorResponse;
|
|
25071
25077
|
/**
|
|
25072
|
-
* `SHARE_IN_USE`: the grantee's resources still
|
|
25078
|
+
* `SHARE_IN_USE`: the grantee's resources still reach the shared resource. `error.meta.references` lists them.
|
|
25073
25079
|
*/
|
|
25074
25080
|
409: ErrorResponse;
|
|
25075
25081
|
/**
|
|
@@ -30742,7 +30748,7 @@ export declare class Shares {
|
|
|
30742
30748
|
/**
|
|
30743
30749
|
* List a grantee's references to a shared resource
|
|
30744
30750
|
*
|
|
30745
|
-
* The grantee project's own resources
|
|
30751
|
+
* The grantee project's own resources a run reaches the resource the share grants from: those naming it (agents binding a shared tool, pipelines stepping through it, ingestion rules converting with it, orchestrations, playbooks, triggers and formations naming it) and, transitively, those naming one of them (deciders and evals on such an agent, workflows dispatching it, triggers firing such an orchestration). Each is listed once, grouped by `type` in the enum's order. What degrades if the project revokes its acceptance, and what `409 SHARE_IN_USE` lists. The grantee is named by `project_id` or by its scoped credential; the publisher holds none of these and is answered `400`.
|
|
30746
30752
|
*/
|
|
30747
30753
|
static listShareReferences<ThrowOnError extends boolean = false>(options: Options<ListShareReferencesData, ThrowOnError>): RequestResult<ListShareReferencesResponses, ListShareReferencesErrors, ThrowOnError>;
|
|
30748
30754
|
/**
|
package/dist/index.mjs
CHANGED
|
@@ -4680,7 +4680,7 @@ var Shares = class {
|
|
|
4680
4680
|
/**
|
|
4681
4681
|
* List a grantee's references to a shared resource
|
|
4682
4682
|
*
|
|
4683
|
-
* The grantee project's own resources
|
|
4683
|
+
* The grantee project's own resources a run reaches the resource the share grants from: those naming it (agents binding a shared tool, pipelines stepping through it, ingestion rules converting with it, orchestrations, playbooks, triggers and formations naming it) and, transitively, those naming one of them (deciders and evals on such an agent, workflows dispatching it, triggers firing such an orchestration). Each is listed once, grouped by `type` in the enum's order. What degrades if the project revokes its acceptance, and what `409 SHARE_IN_USE` lists. The grantee is named by `project_id` or by its scoped credential; the publisher holds none of these and is answered `400`.
|
|
4684
4684
|
*/
|
|
4685
4685
|
static listShareReferences(options) {
|
|
4686
4686
|
return (options.client ?? client).get({
|