@leaflow/sdk 0.190.0 → 0.190.1

package/dist/fleet/v1/generated/validators/replaceMcpConfigurationRequest.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/replaceMcpConfigurationRequest.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/rtcConfiguration.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/rtcConfiguration.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/runCommandRequest.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/runCommandRequest.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/runCommandResponse.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/runCommandResponse.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sendMcpRequestRequest.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sendMcpRequestRequest.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sendMcpRequestResponse.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sendMcpRequestResponse.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionCloseReason.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionCloseReason.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionList.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionList.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionMode.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionMode.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionResource.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionResource.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionState.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/sessionState.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/signedMessage.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/signedMessage.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/signingKey.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/signingKey.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateAccountRequest.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateAccountRequest.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateGroupRequest.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateGroupRequest.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateMachineRequest.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateMachineRequest.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateMcpServerRequest.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateMcpServerRequest.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateMcpServerResponse.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updateMcpServerResponse.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updatePrivilegeAutoApprovalRequest.zod.d.ts

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/fleet/v1/generated/validators/updatePrivilegeAutoApprovalRequest.zod.js

@@ -106,8 +106,7 @@
  * Elevation through sudo is never approved by a password; see "Approving sudo".
  *
  * Members log in over SSH with the SSH keys of their own accounts (`/account/v1/me/ssh-keys` on
- * the account API), while they may log in to the machine. The SSH keys a project shares sign in
- * to no directory account.
+ * the account API), while they may log in to the machine.
  *
  * Machines resolve directory accounts and groups themselves and never write them into their local
  * account files. A local account or group that already uses a name or id of the directory keeps

package/dist/iam/v1/generated/functions.d.ts

@@ -611,7 +611,7 @@ export type createSshKeyResponseError = createSshKeyResponseDefault & {
 export type createSshKeyResponse = createSshKeyResponseSuccess | createSshKeyResponseError;
 export declare const getCreateSshKeyUrl: () => string;
 /**
- * Adds a key the project shares, such as one used by CI or a bastion. Compute installs it on every server created in the project afterwards. It belongs to no member, so it signs in as nobody on Fleet machines; a member adds a key of their own to their account (`POST /account/v1/me/ssh-keys` on the account API).
+ * Adds a key the project shares, such as one used by CI or a bastion. It belongs to the project rather than to the member adding it; a member adds a key of their own to their account (`POST /account/v1/me/ssh-keys` on the account API).
  *
  * Requires `iam:ssh_keys.manage`.
  * @summary Add an SSH key to this project
@@ -675,7 +675,7 @@ export type revokeSshKeyResponseError = revokeSshKeyResponseDefault & {
 export type revokeSshKeyResponse = revokeSshKeyResponseSuccess | revokeSshKeyResponseError;
 export declare const getRevokeSshKeyUrl: (keyId: string) => string;
 /**
- * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time. A server on which Compute installed the key keeps it until it is removed there. Requires `iam:ssh_keys.manage`.
+ * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time. Requires `iam:ssh_keys.manage`.
  * @summary Revoke an SSH key
  */
 export declare const revokeSshKey: (keyId: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<revokeSshKeyResponse>;

package/dist/iam/v1/generated/functions.js

@@ -665,7 +665,7 @@ export const getCreateSshKeyUrl = () => {
     return `https://iam.leaflow.cloud/api/v1/ssh-keys`;
 };
 /**
- * Adds a key the project shares, such as one used by CI or a bastion. Compute installs it on every server created in the project afterwards. It belongs to no member, so it signs in as nobody on Fleet machines; a member adds a key of their own to their account (`POST /account/v1/me/ssh-keys` on the account API).
+ * Adds a key the project shares, such as one used by CI or a bastion. It belongs to the project rather than to the member adding it; a member adds a key of their own to their account (`POST /account/v1/me/ssh-keys` on the account API).
  *
  * Requires `iam:ssh_keys.manage`.
  * @summary Add an SSH key to this project
@@ -748,7 +748,7 @@ export const getRevokeSshKeyUrl = (keyId) => {
     return `https://iam.leaflow.cloud/api/v1/ssh-keys/${encodeURIComponent(String(keyId))}`;
 };
 /**
- * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time. A server on which Compute installed the key keeps it until it is removed there. Requires `iam:ssh_keys.manage`.
+ * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time. Requires `iam:ssh_keys.manage`.
  * @summary Revoke an SSH key
  */
 export const revokeSshKey = async (keyId, options, fetchFn) => {

package/dist/iam/v1/generated/schemas.zod.d.ts

@@ -243,7 +243,7 @@ export declare const ListSshKeysQueryParams: zod.ZodObject<{
     purpose: zod.ZodOptional<zod.ZodString>;
 }, zod.z.core.$strict>;
 /**
- * Adds a key the project shares, such as one used by CI or a bastion. Compute installs it on every server created in the project afterwards. It belongs to no member, so it signs in as nobody on Fleet machines; a member adds a key of their own to their account (`POST /account/v1/me/ssh-keys` on the account API).
+ * Adds a key the project shares, such as one used by CI or a bastion. It belongs to the project rather than to the member adding it; a member adds a key of their own to their account (`POST /account/v1/me/ssh-keys` on the account API).
  *
  * Requires `iam:ssh_keys.manage`.
  * @summary Add an SSH key to this project
@@ -270,7 +270,7 @@ export declare const RenameSshKeyBody: zod.ZodObject<{
     name: zod.ZodString;
 }, zod.z.core.$strict>;
 /**
- * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time. A server on which Compute installed the key keeps it until it is removed there. Requires `iam:ssh_keys.manage`.
+ * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time. Requires `iam:ssh_keys.manage`.
  * @summary Revoke an SSH key
  */
 export declare const RevokeSshKeyParams: zod.ZodObject<{

package/dist/iam/v1/generated/schemas.zod.js

@@ -250,7 +250,7 @@ export const ListSshKeysQueryParams = zod.strictObject({
         .describe("Lists only the keys carrying this purpose. The key the platform generates carries `platform`"),
 });
 /**
- * Adds a key the project shares, such as one used by CI or a bastion. Compute installs it on every server created in the project afterwards. It belongs to no member, so it signs in as nobody on Fleet machines; a member adds a key of their own to their account (`POST /account/v1/me/ssh-keys` on the account API).
+ * Adds a key the project shares, such as one used by CI or a bastion. It belongs to the project rather than to the member adding it; a member adds a key of their own to their account (`POST /account/v1/me/ssh-keys` on the account API).
  *
  * Requires `iam:ssh_keys.manage`.
  * @summary Add an SSH key to this project
@@ -271,7 +271,7 @@ export const RenameSshKeyParams = zod.strictObject({
 });
 export const RenameSshKeyBody = RenameSSHKeyRequestBody;
 /**
- * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time. A server on which Compute installed the key keeps it until it is removed there. Requires `iam:ssh_keys.manage`.
+ * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time. Requires `iam:ssh_keys.manage`.
  * @summary Revoke an SSH key
  */
 export const RevokeSshKeyParams = zod.strictObject({

package/package.json

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