@leaflow/sdk 0.15.0 → 0.16.0

package/dist/compute/v1/schema.d.ts

@@ -501,11 +501,11 @@ export interface paths {
         get?: never;
         /**
          * Replace an instance's labels
-         * @description Records what this instance is for, as key-value pairs, so that a person or an assistant can tell later. Nothing on the platform reads them: no scheduling, quota or billing decision keys off a label, which is what makes editing one safe.
+         * @description Records what this instance is for, as key-value pairs. Nothing on the platform reads them.
          *
-         *     **The whole set is replaced.** Whatever is absent from the request is removed — a merge could not express deleting a key, and it makes retrying the same request produce a different result each time.
+         *     **The whole set is replaced**: whatever is absent from the request is removed.
          *
-         *     Do not put credentials here. Labels appear in listings, in support tickets and in the operator console.
+         *     Do not put credentials here. Labels are visible to platform operators.
          */
         put: operations["set-instance-labels"];
         post?: never;
@@ -525,11 +525,11 @@ export interface paths {
         get?: never;
         /**
          * Replace an instance's note
-         * @description A free-text note: what this instance runs, and what to be careful about before touching it — "primary database, fail over before rebooting". It is read by whoever opens the instance next, including an assistant acting on your behalf.
+         * @description A free-text note about this instance — what it runs, and what to be careful about before touching it.
          *
          *     **The whole note is replaced**; send an empty string to clear it.
          *
-         *     Do not put credentials here. The note appears in the operator console.
+         *     Do not put credentials here. The note is visible to platform operators.
          */
         put: operations["set-instance-notes"];
         post?: never;
@@ -1363,6 +1363,8 @@ export interface components {
             architecture: string;
             /** Format: uuid */
             id: string;
+            /** @description The account this image lets you log in as. The password set at creation belongs to this account */
+            login_username: string;
             /** Format: int64 */
             min_disk_gb: number;
             /** Format: int64 */
@@ -1504,12 +1506,14 @@ export interface components {
             instance_type_id: string;
             /** @description IPv6 address of the primary network interface. Assigned automatically once IPv6 is enabled on the private network */
             ipv6_address: string | null;
-            /** @description Your own classification of this instance, as key-value pairs. Nothing on the platform reads these — they are recorded so that a person, or an assistant acting on your behalf, can tell what an instance is for. Empty when never set */
+            /** @description Your own classification of this instance, as key-value pairs. Empty when never set */
             labels: {
                 [key: string]: string;
             };
+            /** @description The account to log in as over SSH. The password set at creation belongs to this account */
+            login_username: string;
             name: string;
-            /** @description A free-text note about this instance — what it runs, and what to be careful about before touching it. Empty when never set */
+            /** @description A free-text note about this instance. Empty when never set */
             notes: string;
             /**
              * Format: uuid
@@ -1600,7 +1604,7 @@ export interface components {
             password: string;
         };
         SetInstanceLabelsRequestBody: {
-            /** @description The complete set of labels. Whatever is absent here is removed, so this is also how one is deleted; send an empty object to clear them all. A key may not contain a colon, whitespace or control characters — the colon because it separates key from value in the `label` filter */
+            /** @description The complete set of labels. Whatever is absent here is removed; send an empty object to clear them all. A key may not contain a colon, whitespace or control characters */
             labels: {
                 [key: string]: string;
             };
@@ -1624,11 +1628,6 @@ export interface components {
              * @description Kill the command after this long. 60 when omitted
              */
             timeout_seconds?: number;
-            /**
-             * @description The SSH user to log in as. It is the account the platform sets a password for at creation
-             * @default root
-             */
-            username?: string;
         };
         CommandResultResponseBody: {
             /**
@@ -1764,6 +1763,8 @@ export interface components {
             failure: string | null;
             /** Format: uuid */
             id: string;
+            /** @description The account this image lets you log in as. The password set at creation belongs to this account */
+            login_username: string;
             /**
              * Format: int64
              * @description The system disk of an instance created from this image cannot be smaller than this
@@ -2804,7 +2805,7 @@ export interface operations {
     "list-instances": {
         parameters: {
             query?: {
-                /** @description Only instances carrying this label, written as `key:value` — for example `env:prod`. Matched exactly on both halves. A key never contains a colon, so the split is at the first one; anything after it is the value, and `env:` means the key `env` with an empty value rather than "any value" */
+                /** @description Only instances carrying this label, written as `key:value` — for example `env:prod`. Both halves are matched exactly */
                 label?: string;
             };
             header?: never;

package/dist/dns/v1/index.d.ts

@@ -24,14 +24,14 @@ export type ListZonesQuery = operations["list-zones"]["parameters"]["query"];
 export type ListRecordsResult = operations["list-records"]["responses"][200]["content"]["application/json"];
 /** `GET /api/v1/zones/{zone}/records` 的查询参数。 */
 export type ListRecordsQuery = operations["list-records"]["parameters"]["query"];
-/** `POST /api/v1/zones/{zone}/records` 成功时的响应体。 */
-export type AppendRecordsResult = operations["append-records"]["responses"][201]["content"]["application/json"];
-/** `POST /api/v1/zones/{zone}/records` 的查询参数。 */
-export type AppendRecordsQuery = operations["append-records"]["parameters"]["query"];
-/** `POST /api/v1/zones/{zone}/records` 的请求体。 */
-export type AppendRecordsBody = NonNullable<operations["append-records"]["requestBody"]>["content"]["application/json"];
 /** `GET /api/v1/zones/{zone}/records/{name}/{type}` 成功时的响应体。 */
 export type GetRecordSetResult = operations["get-record-set"]["responses"][200]["content"]["application/json"];
+/** `PATCH /api/v1/zones/{zone}/records/{name}/{type}` 成功时的响应体。 */
+export type ModifyRecordSetResult = operations["modify-record-set"]["responses"][200]["content"]["application/json"];
+/** `PATCH /api/v1/zones/{zone}/records/{name}/{type}` 的查询参数。 */
+export type ModifyRecordSetQuery = operations["modify-record-set"]["parameters"]["query"];
+/** `PATCH /api/v1/zones/{zone}/records/{name}/{type}` 的请求体。 */
+export type ModifyRecordSetBody = NonNullable<operations["modify-record-set"]["requestBody"]>["content"]["application/json"];
 /** `PUT /api/v1/zones/{zone}/records/{name}/{type}` 成功时的响应体。 */
 export type SetRecordSetResult = operations["set-record-set"]["responses"][200]["content"]["application/json"];
 /** `PUT /api/v1/zones/{zone}/records/{name}/{type}` 的查询参数。 */

package/dist/dns/v1/schema.d.ts

@@ -150,21 +150,7 @@ export interface paths {
          */
         get: operations["list-records"];
         put?: never;
-        /**
-         * Add records to a record set
-         * @description **Adds values only.** Records already present under the same name and type are left in
-         *     place, and the submitted values are added alongside them.
-         *
-         *     `PUT` states the final contents of a record set, so two concurrent `PUT` requests against
-         *     the same set can discard one another's changes. This operation only adds, and is therefore
-         *     safe to issue concurrently. **Certificate issuance, which places several TXT records under
-         *     `_acme-challenge` at once, must use this operation**: issuing two certificates concurrently
-         *     with `PUT` causes one challenge record to displace the other.
-         *
-         *     The cost is that duplicate values can be created. Use `PUT` to state what a record set
-         *     should contain.
-         */
-        post: operations["append-records"];
+        post?: never;
         delete?: never;
         options?: never;
         head?: never;
@@ -189,21 +175,22 @@ export interface paths {
          *     name and type are the ones listed in `values`; any value present beforehand and absent here
          *     is removed.
          *
-         *     To add a value, retrieve the set with `GET`, append to the values it returns, and submit the
-         *     complete list. Submitting only the new value removes the others; both forms return 200.
-         *
-         *     The record set is created if it does not yet exist, so this operation both creates and
-         *     replaces, and is idempotent.
+         *     The record set is created if it does not exist, so this operation both creates and replaces,
+         *     and is idempotent.
          *
          *     Two concurrent requests against the same domain conflict; the second receives `ZONE_BUSY`
-         *     and may be retried. To add values concurrently, use `POST /records`.
+         *     and may be retried.
+         *
+         *     **Use `PATCH` to add or remove individual values.** Reading the set and submitting a
+         *     modified list is a read-modify-write: values added by anything else between those two steps
+         *     are stated to be absent, and are therefore removed, with both requests returning 200.
          */
         put: operations["set-record-set"];
         post?: never;
         /**
          * Delete a record set
-         * @description Removes every record under this name and type. To remove one value from a set, `PUT` the
-         *     values that should remain.
+         * @description Removes every record under this name and type. **To remove part of a set, use `PATCH`**,
+         *     which is safe to issue concurrently; this operation and `PUT` are not.
          *
          *     Providers reject removal of the last NS record set at the apex of a domain, which would
          *     withdraw the domain from DNS entirely.
@@ -211,7 +198,33 @@ export interface paths {
         delete: operations["delete-record-set"];
         options?: never;
         head?: never;
-        patch?: never;
+        /**
+         * Add or remove values in a record set
+         * @description **Names values to add and remove; anything not named is left in place.** Nothing is read
+         *     first, so this is the only operation on a record set safe to issue concurrently. The set is
+         *     created if it does not exist.
+         *
+         *     Certificate issuance must use this operation for both the challenge record and its cleanup.
+         *     `PUT` and `DELETE` state or remove the whole set, so a concurrent issuance's challenge
+         *     record is discarded — with every request returning 2xx, and the failure surfacing as the
+         *     second certificate failing validation.
+         *
+         *     `add` is applied before `remove`, so a request carrying both changes a value without the
+         *     name ever resolving without it: the set briefly holds one value too many rather than one too
+         *     few. The reverse order, as two requests, leaves a window in which the value is absent — for
+         *     a single-valued set, the name does not resolve at all — and an addition that then fails
+         *     leaves it gone.
+         *
+         *     A value appearing in both `add` and `remove` is rejected rather than resolved in one
+         *     direction.
+         *
+         *     Values in `remove` that are absent are skipped, so a retried cleanup reaches the same
+         *     result. Values in `add` that are already present are rejected by the provider: a record set
+         *     cannot hold the same value twice.
+         *
+         *     Removing every value leaves an empty set, reported as `values: []`, not `RECORD_SET_NOT_FOUND`.
+         */
+        patch: operations["modify-record-set"];
         trace?: never;
     };
 }
@@ -418,18 +431,18 @@ export interface components {
             /** @description The final contents of the record set. Syntax as described on RecordSetResource.values */
             values: string[];
         };
-        AppendRecordsRequestBody: {
-            /** @description The name relative to the domain. `@` denotes the domain itself */
-            name: string;
+        /** @description Names the values to add and to remove. Anything not named is left in place. At least one of `add` and `remove` is required, and no value may appear in both. */
+        ModifyRecordSetRequestBody: {
+            /** @description The values to add. Values already present are rejected by the provider. Syntax as described on RecordSetResource.values */
+            add?: string[];
+            /** @description The values to remove. Values that are not present are skipped. Syntax as described on RecordSetResource.values */
+            remove?: string[];
             /**
              * Format: int64
-             * @description Time to live, in seconds. 0 leaves the choice to the provider
+             * @description Time to live, in seconds, applied to the values in `add`. 0 leaves the choice to the provider. The time to live of values already in the set is not changed; use `PUT` for that
              * @default 300
              */
             ttl?: number;
-            type: components["schemas"]["RecordType"];
-            /** @description The values to add. Syntax as described on RecordSetResource.values */
-            values: string[];
         };
     };
     responses: never;
@@ -712,27 +725,23 @@ export interface operations {
             };
         };
     };
-    "append-records": {
+    "get-record-set": {
         parameters: {
-            query?: {
-                /** @description Which credential to use. When omitted, the credential is determined from the domain; see ZONE_AMBIGUOUS */
-                credential_id?: string;
-            };
+            query?: never;
             header?: never;
             path: {
                 /** @description The domain. A trailing dot is optional */
                 zone: string;
+                /** @description The name, given relative to the domain. `@` denotes the domain itself and `*` a wildcard */
+                name: string;
+                type: components["schemas"]["RecordType"];
             };
             cookie?: never;
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["AppendRecordsRequestBody"];
-            };
-        };
+        requestBody?: never;
         responses: {
-            /** @description Created */
-            201: {
+            /** @description OK */
+            200: {
                 headers: {
                     [name: string]: unknown;
                 };
@@ -751,9 +760,12 @@ export interface operations {
             };
         };
     };
-    "get-record-set": {
+    "set-record-set": {
         parameters: {
-            query?: never;
+            query?: {
+                /** @description Which credential to use. When omitted, the credential is determined from the domain; see ZONE_AMBIGUOUS */
+                credential_id?: string;
+            };
             header?: never;
             path: {
                 /** @description The domain. A trailing dot is optional */
@@ -764,7 +776,11 @@ export interface operations {
             };
             cookie?: never;
         };
-        requestBody?: never;
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["SetRecordSetRequestBody"];
+            };
+        };
         responses: {
             /** @description OK */
             200: {
@@ -786,7 +802,7 @@ export interface operations {
             };
         };
     };
-    "set-record-set": {
+    "delete-record-set": {
         parameters: {
             query?: {
                 /** @description Which credential to use. When omitted, the credential is determined from the domain; see ZONE_AMBIGUOUS */
@@ -802,20 +818,14 @@ export interface operations {
             };
             cookie?: never;
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["SetRecordSetRequestBody"];
-            };
-        };
+        requestBody?: never;
         responses: {
-            /** @description OK */
-            200: {
+            /** @description No Content */
+            204: {
                 headers: {
                     [name: string]: unknown;
                 };
-                content: {
-                    "application/json": components["schemas"]["RecordSetResource"];
-                };
+                content?: never;
             };
             /** @description Error */
             default: {
@@ -828,7 +838,7 @@ export interface operations {
             };
         };
     };
-    "delete-record-set": {
+    "modify-record-set": {
         parameters: {
             query?: {
                 /** @description Which credential to use. When omitted, the credential is determined from the domain; see ZONE_AMBIGUOUS */
@@ -844,14 +854,20 @@ export interface operations {
             };
             cookie?: never;
         };
-        requestBody?: never;
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ModifyRecordSetRequestBody"];
+            };
+        };
         responses: {
-            /** @description No Content */
-            204: {
+            /** @description OK */
+            200: {
                 headers: {
                     [name: string]: unknown;
                 };
-                content?: never;
+                content: {
+                    "application/json": components["schemas"]["RecordSetResource"];
+                };
             };
             /** @description Error */
             default: {

package/dist/index.d.ts

@@ -5,4 +5,6 @@ export type * as compute from "./compute/v1/index.js";
 export type * as dns from "./dns/v1/index.js";
 export type * as iam from "./iam/v1/index.js";
 export type * as monitoring from "./monitoring/v1/index.js";
+export type * as notification from "./notification/v1/index.js";
+export type * as support from "./support/v1/index.js";
 export type * as tunnel from "./tunnel/v1/index.js";

package/dist/monitoring/v1/index.d.ts

@@ -160,3 +160,15 @@ export type GetStatusPageMaintenanceResult = operations["get-status-page-mainten
 export type CancelStatusPageMaintenanceResult = operations["cancel-status-page-maintenance"]["responses"][200]["content"]["application/json"];
 /** `POST /api/v1/status-page/maintenances/{maintenanceId}/complete` 成功时的响应体。 */
 export type CompleteStatusPageMaintenanceResult = operations["complete-status-page-maintenance"]["responses"][200]["content"]["application/json"];
+/** `GET /api/v1/web-checks/{checkId}` 成功时的响应体。 */
+export type GetProjectWebCheckResult = operations["get-project-web-check"]["responses"][200]["content"]["application/json"];
+/** `PUT /api/v1/web-checks/{checkId}` 成功时的响应体。 */
+export type PutProjectWebCheckResult = operations["put-project-web-check"]["responses"][200]["content"]["application/json"];
+/** `PUT /api/v1/web-checks/{checkId}` 的请求体。 */
+export type PutProjectWebCheckBody = NonNullable<operations["put-project-web-check"]["requestBody"]>["content"]["application/json"];
+/** `GET /api/v1/status-page/domain` 成功时的响应体。 */
+export type GetStatusPageDomainResult = operations["get-status-page-domain"]["responses"][200]["content"]["application/json"];
+/** `PUT /api/v1/status-page/domain` 成功时的响应体。 */
+export type PutStatusPageDomainResult = operations["put-status-page-domain"]["responses"][200]["content"]["application/json"];
+/** `PUT /api/v1/status-page/domain` 的请求体。 */
+export type PutStatusPageDomainBody = NonNullable<operations["put-status-page-domain"]["requestBody"]>["content"]["application/json"];