npm - @leaflow/sdk - Versions diffs - 0.190.0 → 0.190.1 - Mend

@leaflow/sdk 0.190.0 → 0.190.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (308) hide show

package/dist/account/v1/generated/validators/invitationResource.zod.d.ts CHANGED Viewed

@@ -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/invitationResource.zod.js CHANGED Viewed

@@ -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/languageOption.zod.d.ts CHANGED Viewed

@@ -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/languageOption.zod.js CHANGED Viewed

@@ -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/lengthAwarePageInvitationResource.zod.d.ts CHANGED Viewed

@@ -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/lengthAwarePageInvitationResource.zod.js CHANGED Viewed

@@ -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/lengthAwarePageProjectAccessResource.zod.d.ts CHANGED Viewed

@@ -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/lengthAwarePageProjectAccessResource.zod.js CHANGED Viewed

@@ -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/lengthAwarePageSSHKeyResource.zod.d.ts CHANGED Viewed

@@ -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/lengthAwarePageSSHKeyResource.zod.js CHANGED Viewed

@@ -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/listMyInvitationsParams.zod.d.ts CHANGED Viewed

@@ -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/listMyInvitationsParams.zod.js CHANGED Viewed

@@ -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/listProjectsParams.zod.d.ts CHANGED Viewed

@@ -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/listProjectsParams.zod.js CHANGED Viewed

@@ -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/listSshKeysParams.zod.d.ts CHANGED Viewed

@@ -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/listSshKeysParams.zod.js CHANGED Viewed

@@ -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/locale.zod.d.ts CHANGED Viewed

@@ -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/locale.zod.js CHANGED Viewed

@@ -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/localeOptionsResource.zod.d.ts CHANGED Viewed

@@ -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/localeOptionsResource.zod.js CHANGED Viewed

@@ -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/offsetPagination.zod.d.ts CHANGED Viewed

@@ -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/offsetPagination.zod.js CHANGED Viewed

@@ -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/previewInvitationByTokenParams.zod.d.ts CHANGED Viewed

@@ -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/previewInvitationByTokenParams.zod.js CHANGED Viewed

@@ -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/projectAccessList.zod.d.ts CHANGED Viewed

@@ -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/projectAccessList.zod.js CHANGED Viewed

@@ -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/projectAccessResource.zod.d.ts CHANGED Viewed

@@ -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/projectAccessResource.zod.js CHANGED Viewed

@@ -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/projectResource.zod.d.ts CHANGED Viewed

@@ -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/projectResource.zod.js CHANGED Viewed

@@ -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/projectSlugAvailabilityResource.zod.d.ts CHANGED Viewed

@@ -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/projectSlugAvailabilityResource.zod.js CHANGED Viewed

@@ -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/projectStatus.zod.d.ts CHANGED Viewed

@@ -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/projectStatus.zod.js CHANGED Viewed

@@ -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/projectTraitResource.zod.d.ts CHANGED Viewed

@@ -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/projectTraitResource.zod.js CHANGED Viewed

@@ -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/registerRequestBody.zod.d.ts CHANGED Viewed

@@ -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/registerRequestBody.zod.js CHANGED Viewed

@@ -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/renameSSHKeyRequestBody.zod.d.ts CHANGED Viewed

@@ -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/renameSSHKeyRequestBody.zod.js CHANGED Viewed

@@ -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/requestAccountDeletionParams.zod.d.ts CHANGED Viewed

@@ -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/requestAccountDeletionParams.zod.js CHANGED Viewed

@@ -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/resourceRefResource.zod.d.ts CHANGED Viewed

@@ -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/resourceRefResource.zod.js CHANGED Viewed

@@ -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/ruleResource.zod.d.ts CHANGED Viewed

@@ -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/ruleResource.zod.js CHANGED Viewed

@@ -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/sSHKeyResource.zod.d.ts CHANGED Viewed

@@ -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/sSHKeyResource.zod.js CHANGED Viewed

@@ -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/scopedTokenResponseBody.zod.d.ts CHANGED Viewed

@@ -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/scopedTokenResponseBody.zod.js CHANGED Viewed

@@ -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/searchProjectsRequestBody.zod.d.ts CHANGED Viewed

@@ -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/searchProjectsRequestBody.zod.js CHANGED Viewed

@@ -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/settingsResource.zod.d.ts CHANGED Viewed

@@ -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/settingsResource.zod.js CHANGED Viewed

@@ -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
  *