@leaflow/sdk 0.0.0-dev.413.g2284e60 → 0.0.0-dev.418.ge62522e

package/dist/compute/v2/generated/functions.d.ts

@@ -225,7 +225,7 @@ export declare const getUpdateElasticIpUrl: (elasticIpId: ElasticIPID) => string
 /**
  * Changes the bandwidth of this elastic IP, or what its pay-as-you-go network subscription charges for. `bandwidth_mbps` and `internet_charge_type` are operational fields: each starts a change and cannot be combined with any other field in the same request. Such a request is refused with 422 `UPDATE_FIELDS_COMBINED`, because a change that committed beside another that was then refused would leave the request half applied. An elastic IP has no descriptive field today, so 200 is reserved for the fields that may be added to it and every accepted update answers 202. `checkout` and `proration_date` belong to the purchase of the `bandwidth_mbps` change and are accepted only together with it.
  *
- * No separate bandwidth resource is created, and the limit applies to inbound and outbound traffic alike. The new value must lie within the line's bandwidth range and step, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. How the change is paid follows the elastic IP's network subscription:
+ * No separate bandwidth resource is created, and the limit applies to inbound and outbound traffic alike. The new value may be any whole number of Mbps within the line's bandwidth range, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. How the change is paid follows the elastic IP's network subscription:
  *
  * - **Prepaid**: the change goes through a Checkout Session that changes the network subscription, priced for the rest of its period. It starts once Billing accepts the order; if checkout is not completed, the order is not accepted or the change fails, `bandwidth_mbps` keeps its value and Billing shows the outcome.
  * - **Pay-as-you-go**: there is no checkout. The change starts at once, `checkout_session_id` and `order_id` are null, and the new limit is metered from the instant it is applied; if it fails, the old limit stays in effect and metered. `checkout` and `proration_date` are refused with `ELASTIC_IP_CHECKOUT_UNUSED`.

package/dist/compute/v2/generated/functions.js

@@ -168,7 +168,7 @@ export const getUpdateElasticIpUrl = (elasticIpId) => {
 /**
  * Changes the bandwidth of this elastic IP, or what its pay-as-you-go network subscription charges for. `bandwidth_mbps` and `internet_charge_type` are operational fields: each starts a change and cannot be combined with any other field in the same request. Such a request is refused with 422 `UPDATE_FIELDS_COMBINED`, because a change that committed beside another that was then refused would leave the request half applied. An elastic IP has no descriptive field today, so 200 is reserved for the fields that may be added to it and every accepted update answers 202. `checkout` and `proration_date` belong to the purchase of the `bandwidth_mbps` change and are accepted only together with it.
  *
- * No separate bandwidth resource is created, and the limit applies to inbound and outbound traffic alike. The new value must lie within the line's bandwidth range and step, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. How the change is paid follows the elastic IP's network subscription:
+ * No separate bandwidth resource is created, and the limit applies to inbound and outbound traffic alike. The new value may be any whole number of Mbps within the line's bandwidth range, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. How the change is paid follows the elastic IP's network subscription:
  *
  * - **Prepaid**: the change goes through a Checkout Session that changes the network subscription, priced for the rest of its period. It starts once Billing accepts the order; if checkout is not completed, the order is not accepted or the change fails, `bandwidth_mbps` keeps its value and Billing shows the outcome.
  * - **Pay-as-you-go**: there is no checkout. The change starts at once, `checkout_session_id` and `order_id` are null, and the new limit is metered from the instant it is applied; if it fails, the old limit stays in effect and metered. `checkout` and `proration_date` are refused with `ELASTIC_IP_CHECKOUT_UNUSED`.

package/dist/compute/v2/generated/models.d.ts

@@ -284,8 +284,6 @@ export interface ElasticIPLine {
     min_bandwidth_mbps: number;
     /** The most bandwidth an elastic IP of this line can be bought with, in Mbps, at most 1000. An elastic IP associated with an instance is also held to the instance type's `max_bandwidth_mbps`. */
     max_bandwidth_mbps: number;
-    /** Bandwidth is bought in multiples of this many Mbps, from `min_bandwidth_mbps` to `max_bandwidth_mbps`, both of which are multiples of it too. */
-    bandwidth_step_mbps: number;
     /** `on_sale` is offered for new elastic IPs; `off_sale` takes none, while the elastic IPs already on it keep working. */
     sale_status: ElasticIPLineSaleStatus;
     /** Whether an elastic IP of this line can be bought with `internet_charge_type` `traffic`, billed by the bytes it sends. `off_sale` refuses that with `ELASTIC_IP_TRAFFIC_UNAVAILABLE`. */
@@ -634,8 +632,8 @@ export interface CreateElasticIPRequestBody {
      * charged nothing for the traffic, while the address itself bills normally — so the invoice
      * looks correct and nothing anywhere reports it.
      *
-     * It must lie within the line's `min_bandwidth_mbps` and `max_bandwidth_mbps` and be a multiple of its
-     * `bandwidth_step_mbps`, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. Changing it
+     * Any whole number of Mbps within the line's `min_bandwidth_mbps` and `max_bandwidth_mbps`, otherwise the
+     * request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. Changing it
      * later updates the same elastic IP through `update-elastic-ip`, not an independent bandwidth resource.
      * @minimum 1
      * @maximum 1000
@@ -1254,7 +1252,7 @@ export interface NewElasticIP {
     type: NewElasticIPType;
     line_id: ElasticIPLineID;
     /**
-     * Within the line's `min_bandwidth_mbps` and `max_bandwidth_mbps` and a multiple of its `bandwidth_step_mbps`, otherwise refused with `ELASTIC_IP_BANDWIDTH_RANGE`.
+     * Any whole number of Mbps within the line's `min_bandwidth_mbps` and `max_bandwidth_mbps`, otherwise refused with `ELASTIC_IP_BANDWIDTH_RANGE`.
      * @minimum 1
      * @maximum 1000
      */

package/dist/compute/v2/generated/schemas.zod.d.ts

@@ -158,7 +158,7 @@ export declare const GetElasticIpParams: zod.ZodObject<{
 /**
  * Changes the bandwidth of this elastic IP, or what its pay-as-you-go network subscription charges for. `bandwidth_mbps` and `internet_charge_type` are operational fields: each starts a change and cannot be combined with any other field in the same request. Such a request is refused with 422 `UPDATE_FIELDS_COMBINED`, because a change that committed beside another that was then refused would leave the request half applied. An elastic IP has no descriptive field today, so 200 is reserved for the fields that may be added to it and every accepted update answers 202. `checkout` and `proration_date` belong to the purchase of the `bandwidth_mbps` change and are accepted only together with it.
  *
- * No separate bandwidth resource is created, and the limit applies to inbound and outbound traffic alike. The new value must lie within the line's bandwidth range and step, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. How the change is paid follows the elastic IP's network subscription:
+ * No separate bandwidth resource is created, and the limit applies to inbound and outbound traffic alike. The new value may be any whole number of Mbps within the line's bandwidth range, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. How the change is paid follows the elastic IP's network subscription:
  *
  * - **Prepaid**: the change goes through a Checkout Session that changes the network subscription, priced for the rest of its period. It starts once Billing accepts the order; if checkout is not completed, the order is not accepted or the change fails, `bandwidth_mbps` keeps its value and Billing shows the outcome.
  * - **Pay-as-you-go**: there is no checkout. The change starts at once, `checkout_session_id` and `order_id` are null, and the new limit is metered from the instant it is applied; if it fails, the old limit stays in effect and metered. `checkout` and `proration_date` are refused with `ELASTIC_IP_CHECKOUT_UNUSED`.

package/dist/compute/v2/generated/schemas.zod.js

@@ -223,7 +223,7 @@ export const GetElasticIpParams = zod.strictObject({
 /**
  * Changes the bandwidth of this elastic IP, or what its pay-as-you-go network subscription charges for. `bandwidth_mbps` and `internet_charge_type` are operational fields: each starts a change and cannot be combined with any other field in the same request. Such a request is refused with 422 `UPDATE_FIELDS_COMBINED`, because a change that committed beside another that was then refused would leave the request half applied. An elastic IP has no descriptive field today, so 200 is reserved for the fields that may be added to it and every accepted update answers 202. `checkout` and `proration_date` belong to the purchase of the `bandwidth_mbps` change and are accepted only together with it.
  *
- * No separate bandwidth resource is created, and the limit applies to inbound and outbound traffic alike. The new value must lie within the line's bandwidth range and step, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. How the change is paid follows the elastic IP's network subscription:
+ * No separate bandwidth resource is created, and the limit applies to inbound and outbound traffic alike. The new value may be any whole number of Mbps within the line's bandwidth range, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. How the change is paid follows the elastic IP's network subscription:
  *
  * - **Prepaid**: the change goes through a Checkout Session that changes the network subscription, priced for the rest of its period. It starts once Billing accepts the order; if checkout is not completed, the order is not accepted or the change fails, `bandwidth_mbps` keeps its value and Billing shows the outcome.
  * - **Pay-as-you-go**: there is no checkout. The change starts at once, `checkout_session_id` and `order_id` are null, and the new limit is metered from the instant it is applied; if it fails, the old limit stays in effect and metered. `checkout` and `proration_date` are refused with `ELASTIC_IP_CHECKOUT_UNUSED`.

package/dist/compute/v2/generated/validators/createElasticIPRequestBody.zod.js

@@ -46,7 +46,7 @@ export const CreateElasticIPRequestBody = zod.strictObject({
         .int()
         .min(1)
         .max(createElasticIPRequestBodyBandwidthMbpsMax)
-        .describe('The bandwidth ceiling of this address, in Mbit/s, applied to both directions.\n\nRequired, and there is no "unlimited": an address with no ceiling runs at line rate and is\ncharged nothing for the traffic, while the address itself bills normally — so the invoice\nlooks correct and nothing anywhere reports it.\n\nIt must lie within the line\'s `min_bandwidth_mbps` and `max_bandwidth_mbps` and be a multiple of its\n`bandwidth_step_mbps`, otherwise the request is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. Changing it\nlater updates the same elastic IP through `update-elastic-ip`, not an independent bandwidth resource.'),
+        .describe('The bandwidth ceiling of this address, in Mbit/s, applied to both directions.\n\nRequired, and there is no "unlimited": an address with no ceiling runs at line rate and is\ncharged nothing for the traffic, while the address itself bills normally — so the invoice\nlooks correct and nothing anywhere reports it.\n\nAny whole number of Mbps within the line\'s `min_bandwidth_mbps` and `max_bandwidth_mbps`, otherwise the\nrequest is refused with `ELASTIC_IP_BANDWIDTH_RANGE`. Changing it\nlater updates the same elastic IP through `update-elastic-ip`, not an independent bandwidth resource.'),
     line_id: ElasticIPLineID,
     billing: BillingChoice,
     checkout: CheckoutOptions.optional(),

package/dist/compute/v2/generated/validators/elasticIPLine.zod.d.ts

@@ -97,7 +97,6 @@ export declare const ElasticIPLine: zod.ZodObject<{
     }, zod.z.core.$strict>;
     min_bandwidth_mbps: zod.ZodInt;
     max_bandwidth_mbps: zod.ZodInt;
-    bandwidth_step_mbps: zod.ZodInt;
     sale_status: zod.ZodEnum<{
         on_sale: "on_sale";
         off_sale: "off_sale";

package/dist/compute/v2/generated/validators/elasticIPLine.zod.js

@@ -53,9 +53,6 @@ export const ElasticIPLine = zod
     max_bandwidth_mbps: zod
         .int()
         .describe("The most bandwidth an elastic IP of this line can be bought with, in Mbps, at most 1000. An elastic IP associated with an instance is also held to the instance type's `max_bandwidth_mbps`."),
-    bandwidth_step_mbps: zod
-        .int()
-        .describe("Bandwidth is bought in multiples of this many Mbps, from `min_bandwidth_mbps` to `max_bandwidth_mbps`, both of which are multiples of it too."),
     sale_status: zod
         .enum(["on_sale", "off_sale"])
         .describe("`on_sale` is offered for new elastic IPs; `off_sale` takes none, while the elastic IPs already on it keep working."),

package/dist/compute/v2/generated/validators/elasticIPLineListResponseBody.zod.d.ts

@@ -95,7 +95,6 @@ export declare const ElasticIPLineListResponseBody: zod.ZodObject<{
         }, zod.z.core.$strict>;
         min_bandwidth_mbps: zod.ZodInt;
         max_bandwidth_mbps: zod.ZodInt;
-        bandwidth_step_mbps: zod.ZodInt;
         sale_status: zod.ZodEnum<{
             on_sale: "on_sale";
             off_sale: "off_sale";

package/dist/compute/v2/generated/validators/newElasticIP.zod.js

@@ -45,7 +45,7 @@ export const NewElasticIP = zod
         .int()
         .min(1)
         .max(newElasticIPBandwidthMbpsMax)
-        .describe("Within the line's `min_bandwidth_mbps` and `max_bandwidth_mbps` and a multiple of its `bandwidth_step_mbps`, otherwise refused with `ELASTIC_IP_BANDWIDTH_RANGE`."),
+        .describe("Any whole number of Mbps within the line's `min_bandwidth_mbps` and `max_bandwidth_mbps`, otherwise refused with `ELASTIC_IP_BANDWIDTH_RANGE`."),
     internet_charge_type: InternetChargeType.optional(),
     billing: BillingChoice.optional(),
 })

package/dist/index.d.ts

@@ -11,3 +11,4 @@ export * as notification from "./notification/v1/index.js";
 export * as support from "./support/v1/index.js";
 export * as type from "./type/index.js";
 export * as swasLegacy from "./swas-legacy/v1/index.js";
+export * as swas from "./swas/v1/index.js";

package/dist/index.js

@@ -11,3 +11,4 @@ export * as notification from "./notification/v1/index.js";
 export * as support from "./support/v1/index.js";
 export * as type from "./type/index.js";
 export * as swasLegacy from "./swas-legacy/v1/index.js";
+export * as swas from "./swas/v1/index.js";

package/dist/routes.d.ts

@@ -4093,5 +4093,85 @@ export declare const routes: readonly [{
     readonly operationId: "list-instance-operations";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: null;
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "GET";
+    readonly path: "/api/v1/catalog/plans";
+    readonly operationId: "list-plans";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "POST";
+    readonly path: "/api/v1/purchases";
+    readonly operationId: "create-purchase";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "GET";
+    readonly path: "/api/v1/purchases/{purchaseId}";
+    readonly operationId: "get-purchase";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "GET";
+    readonly path: "/api/v1/instances";
+    readonly operationId: "list-instances";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "GET";
+    readonly path: "/api/v1/instances/{instanceId}";
+    readonly operationId: "get-instance";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "POST";
+    readonly path: "/api/v1/instances/{instanceId}:start";
+    readonly operationId: "start-instance";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "GET";
+    readonly path: "/api/v1/instances/{instanceId}/operations/{operationId}";
+    readonly operationId: "get-instance-operation";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "POST";
+    readonly path: "/api/v1/instances/{instanceId}:stop";
+    readonly operationId: "stop-instance";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "GET";
+    readonly path: "/api/v1/instances/{instanceId}/cancellations/{cancellationId}/refund-progress";
+    readonly operationId: "get-cancellation-refund-progress";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
+}, {
+    readonly service: "swas";
+    readonly contract: "swas";
+    readonly method: "POST";
+    readonly path: "/api/v1/instances/{instanceId}:reboot";
+    readonly operationId: "reboot-instance";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://swas.leaflow.cloud";
 }];
 export type Route = (typeof routes)[number];

package/dist/routes.js

@@ -4605,4 +4605,94 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: null,
     },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "GET",
+        path: "/api/v1/catalog/plans",
+        operationId: "list-plans",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "POST",
+        path: "/api/v1/purchases",
+        operationId: "create-purchase",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "GET",
+        path: "/api/v1/purchases/{purchaseId}",
+        operationId: "get-purchase",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "GET",
+        path: "/api/v1/instances",
+        operationId: "list-instances",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "GET",
+        path: "/api/v1/instances/{instanceId}",
+        operationId: "get-instance",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "POST",
+        path: "/api/v1/instances/{instanceId}:start",
+        operationId: "start-instance",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "GET",
+        path: "/api/v1/instances/{instanceId}/operations/{operationId}",
+        operationId: "get-instance-operation",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "POST",
+        path: "/api/v1/instances/{instanceId}:stop",
+        operationId: "stop-instance",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "GET",
+        path: "/api/v1/instances/{instanceId}/cancellations/{cancellationId}/refund-progress",
+        operationId: "get-cancellation-refund-progress",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
+    {
+        service: "swas",
+        contract: "swas",
+        method: "POST",
+        path: "/api/v1/instances/{instanceId}:reboot",
+        operationId: "reboot-instance",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://swas.leaflow.cloud",
+    },
 ];