@leaflow/sdk 0.34.0 → 0.35.0

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

@@ -18,6 +18,10 @@ export type ListCreditTransactionsResult = operations["list-credit-transactions"
 export type ReadBillingAccountBalanceResult = operations["read-billing-account-balance"]["responses"][200]["content"]["application/json"];
 /** `PUT /account/v1/billing-accounts/{accountKey}/projects/{projectId}` 成功时的响应体。 */
 export type BindProjectToBillingAccountResult = operations["bind-project-to-billing-account"]["responses"][200]["content"]["application/json"];
+/** `GET /account/v1/billing-accounts/{accountKey}/orders` 成功时的响应体。 */
+export type ListOrdersResult = operations["list-orders"]["responses"][200]["content"]["application/json"];
+/** `GET /account/v1/billing-accounts/{accountKey}/orders/{orderId}` 成功时的响应体。 */
+export type GetOrderResult = operations["get-order"]["responses"][200]["content"]["application/json"];
 /** `GET /account/v1/billing-accounts/{accountKey}/top-ups` 成功时的响应体。 */
 export type ListTopUpsResult = operations["list-top-ups"]["responses"][200]["content"]["application/json"];
 /** `POST /account/v1/billing-accounts/{accountKey}/top-ups` 成功时的响应体。 */

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

@@ -167,6 +167,54 @@ export interface paths {
         patch?: never;
         trace?: never;
     };
+    "/account/v1/billing-accounts/{accountKey}/orders": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * My orders
+         * @description Every provisioning request made against the projects this account pays for, newest first.
+         *
+         *     An order that never went through stays here on purpose. Removing it would leave nothing to
+         *     look at in exactly the case someone wants to look: a resource was asked for, was not
+         *     delivered, and the question is what happened.
+         *
+         *     The list carries no lines. An order has only a handful, but shipping them on every page
+         *     means carrying data no column shows.
+         */
+        get: operations["list-orders"];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    "/account/v1/billing-accounts/{accountKey}/orders/{orderId}": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * One order, with its lines
+         * @description Each line names what was asked for and how much of it. This is the only route that carries
+         *     them.
+         */
+        get: operations["get-order"];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     "/account/v1/billing-accounts/{accountKey}/top-ups": {
         parameters: {
             query?: never;
@@ -638,6 +686,36 @@ export interface components {
         UpdateBillingAccountRequestBody: {
             display_name: string;
         };
+        Order: {
+            id: string;
+            project_id: string;
+            placed_by: string;
+            /**
+             * @description Whether the request went through. It is not the state of what was provisioned: that
+             *     belongs to each resource and outlives the order.
+             * @enum {string}
+             */
+            state: "pending" | "fulfilled" | "failed";
+            failure_reason?: string;
+            /** Format: date-time */
+            created_at: string;
+            /** @description Only present on the single-order route. */
+            lines?: components["schemas"]["OrderLine"][];
+        };
+        OrderLine: {
+            id: string;
+            /** @enum {string} */
+            action: "add" | "renew" | "modify" | "remove";
+            /** @description Which service holds the thing, for example `compute`. */
+            service: string;
+            /** @description That service's own catalogue identifier for what was asked for. */
+            product_id: string;
+            /** Format: int64 */
+            quantity: number;
+        };
+        OrderList: {
+            orders: components["schemas"]["Order"][];
+        };
         TopUpList: {
             top_ups: components["schemas"]["TopUpStatus"][];
         };
@@ -1251,6 +1329,77 @@ export interface operations {
             };
         };
     };
+    "list-orders": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                /**
+                 * @description The account's key, of the form `u_<user_id>_<seq>`. Ownership is stated by the key itself,
+                 *     which is why the key is what addresses the account.
+                 */
+                accountKey: components["parameters"]["AccountKey"];
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description OK */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["OrderList"];
+                };
+            };
+            /** @description Error */
+            default: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["Error"];
+                };
+            };
+        };
+    };
+    "get-order": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                /**
+                 * @description The account's key, of the form `u_<user_id>_<seq>`. Ownership is stated by the key itself,
+                 *     which is why the key is what addresses the account.
+                 */
+                accountKey: components["parameters"]["AccountKey"];
+                orderId: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description OK */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["Order"];
+                };
+            };
+            /** @description Error */
+            default: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["Error"];
+                };
+            };
+        };
+    };
     "list-top-ups": {
         parameters: {
             query?: never;

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

@@ -16,8 +16,12 @@ export type CountUnreadNotificationsQuery = operations["count-unread-notificatio
 export type GetNotificationResult = operations["get-notification"]["responses"][200]["content"]["application/json"];
 /** `POST /api/v1/notifications/{notificationId}/read` 成功时的响应体。 */
 export type MarkNotificationReadResult = operations["mark-notification-read"]["responses"][200]["content"]["application/json"];
+/** `DELETE /api/v1/notifications/{notificationId}/read` 成功时的响应体。 */
+export type MarkNotificationUnreadResult = operations["mark-notification-unread"]["responses"][200]["content"]["application/json"];
 /** `POST /api/v1/notifications/{notificationId}/archive` 成功时的响应体。 */
 export type ArchiveNotificationResult = operations["archive-notification"]["responses"][200]["content"]["application/json"];
+/** `DELETE /api/v1/notifications/{notificationId}/archive` 成功时的响应体。 */
+export type UnarchiveNotificationResult = operations["unarchive-notification"]["responses"][200]["content"]["application/json"];
 /** `GET /api/v1/announcements` 成功时的响应体。 */
 export type ListAnnouncementsResult = operations["list-announcements"]["responses"][200]["content"]["application/json"];
 /** `POST /api/v1/announcements/read` 成功时的响应体。 */

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

@@ -14,9 +14,10 @@ export interface paths {
          * List notifications addressed to you
          * @description Returns notifications in reverse chronological order, newest first.
          *
-         *     Announcements published to the whole platform appear here alongside notifications
-         *     addressed to you individually and are distinguished by `kind`. They are read and archived
-         *     through the same operations.
+         *     Announcements are not in this list. They are one row for the whole platform rather than
+         *     one per reader, so they are listed, read and counted by their own operations under
+         *     `/api/v1/announcements`. `kind` is on every item here for clients that merge the two lists
+         *     themselves, and it is `notification` for everything this operation returns.
          */
         get: operations["list-notifications"];
         put?: never;
@@ -107,7 +108,14 @@ export interface paths {
          * @description Marking a notification that is already read succeeds and changes nothing.
          */
         post: operations["mark-notification-read"];
-        delete?: never;
+        /**
+         * Mark one notification as unread
+         * @description Puts it back in the unread count, which is what somebody wants after opening a thing by
+         *     accident and needing it to stay in front of them.
+         *
+         *     Marking one that is already unread succeeds and changes nothing.
+         */
+        delete: operations["mark-notification-unread"];
         options?: never;
         head?: never;
         patch?: never;
@@ -128,7 +136,18 @@ export interface paths {
          *     `include_archived` to see it again. Archiving also marks it read.
          */
         post: operations["archive-notification"];
-        delete?: never;
+        /**
+         * Take one notification out of the archive
+         * @description Returns it to the default listing. Archiving is one click away from anything in the list,
+         *     so undoing it has to be too; without this operation a mistaken archive is permanent, and
+         *     the notification stays reachable only by asking for archived ones.
+         *
+         *     It does not mark it unread again: archiving marked it read, and that it was read is still
+         *     true. Use `mark-notification-unread` for that.
+         *
+         *     Unarchiving one that is not archived succeeds and changes nothing.
+         */
+        delete: operations["unarchive-notification"];
         options?: never;
         head?: never;
         patch?: never;
@@ -1142,6 +1161,38 @@ export interface operations {
             };
         };
     };
+    "mark-notification-unread": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                /** @description The notification, or the announcement when kind is announcement */
+                notificationId: components["parameters"]["NotificationId"];
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description OK */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["NotificationResource"];
+                };
+            };
+            /** @description Error */
+            default: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["Error"];
+                };
+            };
+        };
+    };
     "archive-notification": {
         parameters: {
             query?: never;
@@ -1174,6 +1225,38 @@ export interface operations {
             };
         };
     };
+    "unarchive-notification": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                /** @description The notification, or the announcement when kind is announcement */
+                notificationId: components["parameters"]["NotificationId"];
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description OK */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["NotificationResource"];
+                };
+            };
+            /** @description Error */
+            default: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["Error"];
+                };
+            };
+        };
+    };
     "list-announcements": {
         parameters: {
             query?: never;

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

@@ -18,8 +18,8 @@ export interface paths {
          *     pages, which are reached before a project has been selected. It returns a narrower shape
          *     than the authenticated operations and is not paginated.
          *
-         *     Platform announcements are not served here. They belong to the notification service, which
-         *     owns announcements for the whole platform.
+         *     Platform announcements are not part of this API. They are served by the notification
+         *     service, which owns platform-wide announcements.
          */
         get: operations["list-notices"];
         put?: never;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.34.0",
+  "version": "0.35.0",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {