@leaflow/sdk 0.190.0 → 0.191.0

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

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *
@@ -370,8 +370,6 @@ export type createSshKeyResponseError = createSshKeyResponseDefault & {
 export type createSshKeyResponse = createSshKeyResponseSuccess | createSshKeyResponseError;
 export declare const getCreateSshKeyUrl: () => string;
 /**
- * The key takes effect in every project the caller belongs to: Fleet machines accept it within about a minute, and Compute installs it on the servers the caller creates or reinstalls from then on.
- *
  * Fails with 409 `SSH_KEY_ALREADY_EXISTS` while the same key is active on any account, this one included, and with 412 `SSH_KEY_QUOTA_EXCEEDED` while the account already holds 50 active keys.
  * @summary Add an SSH key to the current account
  */
@@ -434,7 +432,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. Fleet machines stop accepting the key within about a minute. A server on which Compute installed the key keeps it until it is removed there.
+ * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time.
  *
  * The same key can then be added again, to this account or another.
  * @summary Revoke an SSH key of the current account

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

@@ -337,8 +337,6 @@ export const getCreateSshKeyUrl = () => {
     return `https://account.leaflow.cloud/account/v1/me/ssh-keys`;
 };
 /**
- * The key takes effect in every project the caller belongs to: Fleet machines accept it within about a minute, and Compute installs it on the servers the caller creates or reinstalls from then on.
- *
  * Fails with 409 `SSH_KEY_ALREADY_EXISTS` while the same key is active on any account, this one included, and with 412 `SSH_KEY_QUOTA_EXCEEDED` while the account already holds 50 active keys.
  * @summary Add an SSH key to the current account
  */
@@ -420,7 +418,7 @@ export const getRevokeSshKeyUrl = (keyId) => {
     return `https://account.leaflow.cloud/account/v1/me/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. Fleet machines stop accepting the key within about a minute. A server on which Compute installed the key keeps it until it is removed there.
+ * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time.
  *
  * The same key can then be added again, to this account or another.
  * @summary Revoke an SSH key of the current account

package/dist/account/v1/generated/models.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

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

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *
@@ -118,8 +118,6 @@ export declare const ListSshKeysQueryParams: zod.ZodObject<{
     }>>;
 }, zod.z.core.$strict>;
 /**
- * The key takes effect in every project the caller belongs to: Fleet machines accept it within about a minute, and Compute installs it on the servers the caller creates or reinstalls from then on.
- *
  * Fails with 409 `SSH_KEY_ALREADY_EXISTS` while the same key is active on any account, this one included, and with 412 `SSH_KEY_QUOTA_EXCEEDED` while the account already holds 50 active keys.
  * @summary Add an SSH key to the current account
  */
@@ -144,7 +142,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. Fleet machines stop accepting the key within about a minute. A server on which Compute installed the key keeps it until it is removed there.
+ * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time.
  *
  * The same key can then be added again, to this account or another.
  * @summary Revoke an SSH key of the current account

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

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *
@@ -104,8 +104,6 @@ export const ListSshKeysQueryParams = zod.strictObject({
         .describe("Both kinds are returned while this is absent"),
 });
 /**
- * The key takes effect in every project the caller belongs to: Fleet machines accept it within about a minute, and Compute installs it on the servers the caller creates or reinstalls from then on.
- *
  * Fails with 409 `SSH_KEY_ALREADY_EXISTS` while the same key is active on any account, this one included, and with 412 `SSH_KEY_QUOTA_EXCEEDED` while the account already holds 50 active keys.
  * @summary Add an SSH key to the current account
  */
@@ -125,7 +123,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. Fleet machines stop accepting the key within about a minute. A server on which Compute installed the key keeps it until it is removed there.
+ * The row remains and its status becomes `REVOKED`, so it stays answerable afterwards which key was trusted at the time.
  *
  * The same key can then be added again, to this account or another.
  * @summary Revoke an SSH key of the current account

package/dist/account/v1/generated/validators/acceptConsentsRequestBody.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/acceptConsentsRequestBody.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/acceptInvitationByTokenRequestBody.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/acceptInvitationByTokenRequestBody.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/acceptedInvitationResponseBody.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/acceptedInvitationResponseBody.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/accountDeletionObjectionResource.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/accountDeletionObjectionResource.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/accountDeletionResource.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/accountDeletionResource.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/accountDeletionState.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/accountDeletionState.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/accountResource.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/accountResource.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/agreementListResponseBody.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/agreementListResponseBody.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/agreementResource.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/agreementResource.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/consentBody.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/consentBody.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/consentListResponseBody.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/consentListResponseBody.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/consentResource.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/consentResource.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/countryOption.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/countryOption.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/createProjectRequestBody.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/createProjectRequestBody.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/createSSHKeyRequestBody.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/createSSHKeyRequestBody.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/cursorPagination.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/cursorPagination.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/error.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/error.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/errorStatus.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/errorStatus.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/fieldViolation.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/fieldViolation.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/grantResource.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/grantResource.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/identityVerificationResource.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/identityVerificationResource.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/invitationPreviewResource.zod.d.ts

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *

package/dist/account/v1/generated/validators/invitationPreviewResource.zod.js

@@ -18,7 +18,7 @@
  *
  * ## SSH keys
  *
- * The SSH keys of an account sign its holder in as themselves, in every project they belong to: Fleet machines accept them for the holder's directory account wherever `fleet:machines.login` allows it, and Compute installs them on the servers the holder creates or reinstalls. A key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
+ * The SSH keys of an account belong to its holder rather than to any project, and a key is active on one account at most. Keys shared by a project, such as one used by CI, belong to the project instead and are managed through the IAM API.
  *
  * ## Project slugs
  *