@leaflow/sdk 0.197.0 → 0.198.0

package/dist/iam/v1/generated/validators/resourceTypeResource.zod.d.ts

@@ -1,20 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow IAM API
- * What happens inside a project: members, roles, invitations and the SSH keys the project shares.
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
- * `projectId`, and the current project is the one the token states. Tokens are obtained from the
- * account API.
- *
- * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
- * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const ResourceTypeResource: zod.ZodObject<{
-    name: zod.ZodString;
-}, zod.z.core.$strict>;
-export type ResourceTypeResource = zod.input<typeof ResourceTypeResource>;
-export type ResourceTypeResourceOutput = zod.output<typeof ResourceTypeResource>;

package/dist/iam/v1/generated/validators/resourceTypeResource.zod.js

@@ -1,20 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow IAM API
- * What happens inside a project: members, roles, invitations and the SSH keys the project shares.
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
- * `projectId`, and the current project is the one the token states. Tokens are obtained from the
- * account API.
- *
- * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
- * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export const ResourceTypeResource = zod.strictObject({
-    name: zod
-        .string()
-        .describe("The code of the resource type, such as dns:zone. There is no display name here either; what it reads as is decided by the layer rendering it"),
-});

package/dist/iam/v1/generated/validators/setMemberPermissionsRequestBody.zod.d.ts

@@ -1,20 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow IAM API
- * What happens inside a project: members, roles, invitations and the SSH keys the project shares.
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
- * `projectId`, and the current project is the one the token states. Tokens are obtained from the
- * account API.
- *
- * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
- * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const SetMemberPermissionsRequestBody: zod.ZodObject<{
-    permissions: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-}, zod.z.core.$strict>;
-export type SetMemberPermissionsRequestBody = zod.input<typeof SetMemberPermissionsRequestBody>;
-export type SetMemberPermissionsRequestBodyOutput = zod.output<typeof SetMemberPermissionsRequestBody>;

package/dist/iam/v1/generated/validators/setMemberPermissionsRequestBody.zod.js

@@ -1,21 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow IAM API
- * What happens inside a project: members, roles, invitations and the SSH keys the project shares.
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
- * `projectId`, and the current project is the one the token states. Tokens are obtained from the
- * account API.
- *
- * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
- * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export const SetMemberPermissionsRequestBody = zod.strictObject({
-    permissions: zod
-        .array(zod.string())
-        .nullable()
-        .describe("**Every** permission name to be attached directly to this person, replaced in full. The permissions a role grants are neither listed here nor touched by this write"),
-});

package/dist/iam/v1/generated/validators/updatePolicyRequestBody.zod.js

@@ -1,39 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow IAM API
- * What happens inside a project: members, roles, invitations and the SSH keys the project shares.
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme. No path carries a
- * `projectId`, and the current project is the one the token states. Tokens are obtained from the
- * account API.
- *
- * `GET /api/v1/membership` returns the roles and permissions the caller holds in the current
- * project. It does not state whether a given operation is allowed; each service declares which permission its own operations require.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-import { ResourceRefResource } from "./resourceRefResource.zod.js";
-export const updatePolicyRequestBodyDescriptionMax = 255;
-export const UpdatePolicyRequestBody = zod.strictObject({
-    description: zod
-        .string()
-        .max(updatePolicyRequestBodyDescriptionMax)
-        .optional()
-        .describe("Why it was granted, written for a reader. It is replaced together with the change, so that what remains does not explain an earlier version"),
-    effect: zod
-        .enum(["allow", "deny"])
-        .describe("Must match the current effect of the policy. The effect itself cannot be changed; delete the policy and create another instead. It is still required in the request because the write replaces the policy in full, and omitting it would let a caller believe an effect had been changed while the field was ignored. A mismatch answers PROJECT_POLICY_EFFECT_IMMUTABLE"),
-    permissions: zod
-        .array(zod.string())
-        .nullish()
-        .describe("Permission names attached directly, replaced in full. Anything not listed is withdrawn rather than kept"),
-    resources: zod
-        .array(ResourceRefResource)
-        .nullish()
-        .describe("The resource scope of this policy, replaced in full. What the scope contains can change; whether the policy has one cannot. A base policy cannot take a scope, and a scoped policy cannot have its scope cleared"),
-    roles: zod
-        .array(zod.string())
-        .nullish()
-        .describe("Each must be a role already defined in this project, replaced in full. As when attaching, `OWNER` and `ADMIN` are not accepted"),
-});