@meshery/schemas 1.3.90 → 1.3.92
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.
- package/dist/cloudApi.d.mts +4351 -4351
- package/dist/cloudApi.d.ts +4351 -4351
- package/dist/cloudApi.js +1 -1
- package/dist/cloudApi.mjs +1 -1
- package/dist/constructs/v1beta1/organization_smtp/OrganizationSmtp.d.ts +3 -3
- package/dist/constructs/v1beta1/organization_smtp/OrganizationSmtpSchema.js +1 -1
- package/dist/constructs/v1beta1/organization_smtp/OrganizationSmtpSchema.mjs +1 -1
- package/dist/constructs/v1beta1/registry/Registry.d.ts +9 -9
- package/dist/constructs/v1beta1/registry/RegistrySchema.js +3 -3
- package/dist/constructs/v1beta1/registry/RegistrySchema.mjs +3 -3
- package/dist/constructs/v1beta3/activity_result/ActivityResult.d.ts +1 -1
- package/dist/constructs/v1beta3/activity_result/ActivityResultSchema.js +1 -1
- package/dist/constructs/v1beta3/activity_result/ActivityResultSchema.mjs +1 -1
- package/dist/constructs/v1beta3/connection/Connection.d.ts +27 -27
- package/dist/constructs/v1beta3/connection/ConnectionSchema.js +3 -3
- package/dist/constructs/v1beta3/connection/ConnectionSchema.mjs +3 -3
- package/dist/constructs/v1beta3/{content_piece/ContentPiece.d.ts → content_item/ContentItem.d.ts} +96 -96
- package/dist/constructs/v1beta3/content_item/ContentItemSchema.d.ts +2 -0
- package/dist/constructs/v1beta3/content_item/ContentItemSchema.js +71 -0
- package/dist/constructs/v1beta3/content_item/ContentItemSchema.mjs +71 -0
- package/dist/constructs/v1beta3/environment/Environment.d.ts +29 -29
- package/dist/constructs/v1beta3/environment/EnvironmentSchema.js +1 -1
- package/dist/constructs/v1beta3/environment/EnvironmentSchema.mjs +1 -1
- package/dist/constructs/v1beta3/profile/Profile.d.ts +10 -7
- package/dist/constructs/v1beta3/profile/ProfileSchema.js +8 -5
- package/dist/constructs/v1beta3/profile/ProfileSchema.mjs +8 -5
- package/dist/constructs/v1beta3/workspace/Workspace.d.ts +5 -5
- package/dist/constructs/v1beta3/workspace/WorkspaceSchema.js +2 -2
- package/dist/constructs/v1beta3/workspace/WorkspaceSchema.mjs +2 -2
- package/dist/mesheryApi.d.mts +44 -44
- package/dist/mesheryApi.d.ts +44 -44
- package/dist/permissions.d.mts +29 -29
- package/dist/permissions.d.ts +29 -29
- package/dist/permissions.js +1 -1
- package/dist/permissions.mjs +1 -1
- package/package.json +1 -1
- package/dist/constructs/v1beta3/content_piece/ContentPieceSchema.d.ts +0 -2
- package/dist/constructs/v1beta3/content_piece/ContentPieceSchema.js +0 -71
- package/dist/constructs/v1beta3/content_piece/ContentPieceSchema.mjs +0 -71
- /package/dist/constructs/v1beta3/{content_piece/ContentPiece.js → content_item/ContentItem.js} +0 -0
- /package/dist/constructs/v1beta3/{content_piece/ContentPiece.mjs → content_item/ContentItem.mjs} +0 -0
package/dist/mesheryApi.d.ts
CHANGED
|
@@ -6701,16 +6701,16 @@ type RegisterRegistryComponentApiArg = {
|
|
|
6701
6701
|
updatedAt?: string;
|
|
6702
6702
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
6703
6703
|
deletedAt?: string | null;
|
|
6704
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
6704
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
6705
6705
|
|
|
6706
6706
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
6707
6707
|
|
|
6708
6708
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
6709
6709
|
|
|
6710
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
6710
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
6711
6711
|
|
|
6712
6712
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
6713
|
-
purpose?: "user" | "administrative"
|
|
6713
|
+
purpose?: "user" | "administrative";
|
|
6714
6714
|
}[];
|
|
6715
6715
|
/** Specifies the version of the schema used for the definition. */
|
|
6716
6716
|
schemaVersion: string;
|
|
@@ -7402,16 +7402,16 @@ type RegisterRegistryRelationshipApiArg = {
|
|
|
7402
7402
|
updatedAt?: string;
|
|
7403
7403
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
7404
7404
|
deletedAt?: string | null;
|
|
7405
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
7405
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
7406
7406
|
|
|
7407
7407
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
7408
7408
|
|
|
7409
7409
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
7410
7410
|
|
|
7411
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
7411
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
7412
7412
|
|
|
7413
7413
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
7414
|
-
purpose?: "user" | "administrative"
|
|
7414
|
+
purpose?: "user" | "administrative";
|
|
7415
7415
|
}[];
|
|
7416
7416
|
/** Specifies the version of the schema used for the definition. */
|
|
7417
7417
|
schemaVersion: string;
|
|
@@ -10842,16 +10842,16 @@ type GetConnectionsApiResponse = {
|
|
|
10842
10842
|
updatedAt?: string;
|
|
10843
10843
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
10844
10844
|
deletedAt?: string | null;
|
|
10845
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
10845
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
10846
10846
|
|
|
10847
10847
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
10848
10848
|
|
|
10849
10849
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
10850
10850
|
|
|
10851
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
10851
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
10852
10852
|
|
|
10853
10853
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
10854
|
-
purpose?: "user" | "administrative"
|
|
10854
|
+
purpose?: "user" | "administrative";
|
|
10855
10855
|
}[];
|
|
10856
10856
|
/** Specifies the version of the schema used for the definition. */
|
|
10857
10857
|
schemaVersion: string;
|
|
@@ -11112,16 +11112,16 @@ type RegisterConnectionApiResponse = {
|
|
|
11112
11112
|
updatedAt?: string;
|
|
11113
11113
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
11114
11114
|
deletedAt?: string | null;
|
|
11115
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
11115
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
11116
11116
|
|
|
11117
11117
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
11118
11118
|
|
|
11119
11119
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
11120
11120
|
|
|
11121
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
11121
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
11122
11122
|
|
|
11123
11123
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
11124
|
-
purpose?: "user" | "administrative"
|
|
11124
|
+
purpose?: "user" | "administrative";
|
|
11125
11125
|
}[];
|
|
11126
11126
|
/** Specifies the version of the schema used for the definition. */
|
|
11127
11127
|
schemaVersion: string;
|
|
@@ -11348,16 +11348,16 @@ type RegisterConnectionApiResponse = {
|
|
|
11348
11348
|
updatedAt?: string;
|
|
11349
11349
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
11350
11350
|
deletedAt?: string | null;
|
|
11351
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
11351
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
11352
11352
|
|
|
11353
11353
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
11354
11354
|
|
|
11355
11355
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
11356
11356
|
|
|
11357
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
11357
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
11358
11358
|
|
|
11359
11359
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
11360
|
-
purpose?: "user" | "administrative"
|
|
11360
|
+
purpose?: "user" | "administrative";
|
|
11361
11361
|
}[];
|
|
11362
11362
|
/** Specifies the version of the schema used for the definition. */
|
|
11363
11363
|
schemaVersion: string;
|
|
@@ -11786,16 +11786,16 @@ type GetConnectionByIdApiResponse = {
|
|
|
11786
11786
|
updatedAt?: string;
|
|
11787
11787
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
11788
11788
|
deletedAt?: string | null;
|
|
11789
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
11789
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
11790
11790
|
|
|
11791
11791
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
11792
11792
|
|
|
11793
11793
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
11794
11794
|
|
|
11795
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
11795
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
11796
11796
|
|
|
11797
11797
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
11798
|
-
purpose?: "user" | "administrative"
|
|
11798
|
+
purpose?: "user" | "administrative";
|
|
11799
11799
|
}[];
|
|
11800
11800
|
/** Specifies the version of the schema used for the definition. */
|
|
11801
11801
|
schemaVersion: string;
|
|
@@ -12027,16 +12027,16 @@ type UpdateConnectionApiResponse = {
|
|
|
12027
12027
|
updatedAt?: string;
|
|
12028
12028
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
12029
12029
|
deletedAt?: string | null;
|
|
12030
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
12030
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
12031
12031
|
|
|
12032
12032
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
12033
12033
|
|
|
12034
12034
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
12035
12035
|
|
|
12036
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
12036
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
12037
12037
|
|
|
12038
12038
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
12039
|
-
purpose?: "user" | "administrative"
|
|
12039
|
+
purpose?: "user" | "administrative";
|
|
12040
12040
|
}[];
|
|
12041
12041
|
/** Specifies the version of the schema used for the definition. */
|
|
12042
12042
|
schemaVersion: string;
|
|
@@ -12430,16 +12430,16 @@ type PerformConnectionActionApiResponse =
|
|
|
12430
12430
|
updatedAt?: string;
|
|
12431
12431
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
12432
12432
|
deletedAt?: string | null;
|
|
12433
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
12433
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
12434
12434
|
|
|
12435
12435
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
12436
12436
|
|
|
12437
12437
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
12438
12438
|
|
|
12439
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
12439
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
12440
12440
|
|
|
12441
12441
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
12442
|
-
purpose?: "user" | "administrative"
|
|
12442
|
+
purpose?: "user" | "administrative";
|
|
12443
12443
|
}[];
|
|
12444
12444
|
/** Specifies the version of the schema used for the definition. */
|
|
12445
12445
|
schemaVersion: string;
|
|
@@ -13214,16 +13214,16 @@ type CreateEnvironmentApiResponse = {
|
|
|
13214
13214
|
updatedAt?: string;
|
|
13215
13215
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
13216
13216
|
deletedAt?: string | null;
|
|
13217
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
13217
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
13218
13218
|
|
|
13219
13219
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
13220
13220
|
|
|
13221
13221
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
13222
13222
|
|
|
13223
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
13223
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
13224
13224
|
|
|
13225
13225
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
13226
|
-
purpose?: "user" | "administrative"
|
|
13226
|
+
purpose?: "user" | "administrative";
|
|
13227
13227
|
};
|
|
13228
13228
|
type CreateEnvironmentApiArg = {
|
|
13229
13229
|
/** Body for creating environment */
|
|
@@ -13238,8 +13238,8 @@ type CreateEnvironmentApiArg = {
|
|
|
13238
13238
|
metadata?: {
|
|
13239
13239
|
[key: string]: any;
|
|
13240
13240
|
};
|
|
13241
|
-
/** The
|
|
13242
|
-
purpose?: "user"
|
|
13241
|
+
/** The purpose a client may give an environment on create or update: `user` (an ordinary environment). Profiles are not environments; they are their own construct at `/api/profiles`, assigned to workspaces. Omitted means `user` on create and unchanged on update. A server refuses any other value with 400, and never lets this field change an environment that already carries a privileged purpose. */
|
|
13242
|
+
purpose?: "user";
|
|
13243
13243
|
};
|
|
13244
13244
|
};
|
|
13245
13245
|
type GetEnvironmentsApiResponse = {
|
|
@@ -13271,16 +13271,16 @@ type GetEnvironmentsApiResponse = {
|
|
|
13271
13271
|
updatedAt?: string;
|
|
13272
13272
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
13273
13273
|
deletedAt?: string | null;
|
|
13274
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
13274
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
13275
13275
|
|
|
13276
13276
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
13277
13277
|
|
|
13278
13278
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
13279
13279
|
|
|
13280
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
13280
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
13281
13281
|
|
|
13282
13282
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
13283
|
-
purpose?: "user" | "administrative"
|
|
13283
|
+
purpose?: "user" | "administrative";
|
|
13284
13284
|
}[];
|
|
13285
13285
|
};
|
|
13286
13286
|
type GetEnvironmentsApiArg = {
|
|
@@ -13297,7 +13297,7 @@ type GetEnvironmentsApiArg = {
|
|
|
13297
13297
|
/** User's organization ID */
|
|
13298
13298
|
orgId: string;
|
|
13299
13299
|
/** Return only environments with this purpose; absent returns every purpose the caller may see. The filter only narrows the environments the caller can already list and grants no visibility - a caller who cannot see administrative environments receives an empty page for purpose=administrative. */
|
|
13300
|
-
purpose?: "user" | "administrative"
|
|
13300
|
+
purpose?: "user" | "administrative";
|
|
13301
13301
|
};
|
|
13302
13302
|
type GetEnvironmentByIdApiResponse = {
|
|
13303
13303
|
/** Zero-based page index returned in this response. */
|
|
@@ -13328,16 +13328,16 @@ type GetEnvironmentByIdApiResponse = {
|
|
|
13328
13328
|
updatedAt?: string;
|
|
13329
13329
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
13330
13330
|
deletedAt?: string | null;
|
|
13331
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
13331
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
13332
13332
|
|
|
13333
13333
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
13334
13334
|
|
|
13335
13335
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
13336
13336
|
|
|
13337
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
13337
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
13338
13338
|
|
|
13339
13339
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
13340
|
-
purpose?: "user" | "administrative"
|
|
13340
|
+
purpose?: "user" | "administrative";
|
|
13341
13341
|
}[];
|
|
13342
13342
|
};
|
|
13343
13343
|
type GetEnvironmentByIdApiArg = {
|
|
@@ -13375,16 +13375,16 @@ type UpdateEnvironmentApiResponse = {
|
|
|
13375
13375
|
updatedAt?: string;
|
|
13376
13376
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
13377
13377
|
deletedAt?: string | null;
|
|
13378
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
13378
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
13379
13379
|
|
|
13380
13380
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
13381
13381
|
|
|
13382
13382
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
13383
13383
|
|
|
13384
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
13384
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
13385
13385
|
|
|
13386
13386
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
13387
|
-
purpose?: "user" | "administrative"
|
|
13387
|
+
purpose?: "user" | "administrative";
|
|
13388
13388
|
}[];
|
|
13389
13389
|
};
|
|
13390
13390
|
type UpdateEnvironmentApiArg = {
|
|
@@ -13402,8 +13402,8 @@ type UpdateEnvironmentApiArg = {
|
|
|
13402
13402
|
metadata?: {
|
|
13403
13403
|
[key: string]: any;
|
|
13404
13404
|
};
|
|
13405
|
-
/** The
|
|
13406
|
-
purpose?: "user"
|
|
13405
|
+
/** The purpose a client may give an environment on create or update: `user` (an ordinary environment). Profiles are not environments; they are their own construct at `/api/profiles`, assigned to workspaces. Omitted means `user` on create and unchanged on update. A server refuses any other value with 400, and never lets this field change an environment that already carries a privileged purpose. */
|
|
13406
|
+
purpose?: "user";
|
|
13407
13407
|
};
|
|
13408
13408
|
};
|
|
13409
13409
|
type DeleteEnvironmentApiResponse = unknown;
|
|
@@ -14273,16 +14273,16 @@ type GetEnvironmentsOfWorkspaceApiResponse = {
|
|
|
14273
14273
|
updatedAt?: string;
|
|
14274
14274
|
/** Timestamp when the environment was soft deleted. Null while the environment remains active. */
|
|
14275
14275
|
deletedAt?: string | null;
|
|
14276
|
-
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust.
|
|
14276
|
+
/** What the environment exists for. `user` is an ordinary environment that people create to logically group Connections and their Credentials. `administrative` designates an environment the platform itself provisions to hold organization-level configuration, and which resolvers of that configuration therefore trust. Profiles are not environments: they are their own construct (`schemas/constructs/v1beta3/profile`, served at `/api/profiles` and assigned to workspaces under `/api/workspaces/{workspaceId}/profiles`).
|
|
14277
14277
|
|
|
14278
14278
|
Absent means `user`. Nothing may read an unset or unrecognised value as administrative: test for the administrative value explicitly rather than for "not user", so the property fails closed.
|
|
14279
14279
|
|
|
14280
14280
|
At most one live environment per organization may carry any single privileged purpose - `administrative`, and each privileged value a later version adds. Name those values explicitly wherever the rule is enforced, including the database index predicate: a "not `user`" test also matches the empty value that unmigrated rows and un-normalised writes read back as, which means ordinary. A resolver that selects an environment by purpose MUST fail closed when more than one live row matches: return an error rather than whichever row the database happened to return first.
|
|
14281
14281
|
|
|
14282
|
-
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged
|
|
14282
|
+
Privileged values are server-owned and never client-settable. `EnvironmentPayload`, which every environment POST and PUT requestBody references, accepts only the non-privileged value `user`, and the create-or-edit form has no field for it, so the environment create and update endpoints cannot designate an environment administrative. That restriction is a codegen guarantee, never access control: the registrant connection inlines the full environment entity, so `registerRegistryComponent` and `registerRegistryRelationship` do carry `purpose` in a request type and consumers MUST refuse it on input there too. Whatever surface a value arrives on, every consumer MUST assign this property only from server-side provisioning or a data migration. Permission to create an environment does not confer the ability to make one administrative.
|
|
14283
14283
|
|
|
14284
14284
|
The database index that enforces the uniqueness invariant, the migration path for environments that are administrative by naming convention today, and each consumer's obligations are specified in https://github.com/meshery/schemas/blob/master/docs/environment-purpose-contract.md. */
|
|
14285
|
-
purpose?: "user" | "administrative"
|
|
14285
|
+
purpose?: "user" | "administrative";
|
|
14286
14286
|
}[];
|
|
14287
14287
|
};
|
|
14288
14288
|
type GetEnvironmentsOfWorkspaceApiArg = {
|
package/dist/permissions.d.mts
CHANGED
|
@@ -23,7 +23,7 @@ interface Key {
|
|
|
23
23
|
/**
|
|
24
24
|
* Permissions Index ID used for this generated file.
|
|
25
25
|
*/
|
|
26
|
-
declare const PERMISSIONS_INDEX_ID: "
|
|
26
|
+
declare const PERMISSIONS_INDEX_ID: "1842d28fff5ae8af85366dd952d0d47c8e78c48d4bff56cf67fb856ac1b95463";
|
|
27
27
|
/**
|
|
28
28
|
* Creates a PermissionKey from a UUID string.
|
|
29
29
|
* @param uuid - The UUID string to convert
|
|
@@ -455,44 +455,44 @@ declare const Keys: {
|
|
|
455
455
|
readonly description: "Delete WASM filter permanently from catalog.";
|
|
456
456
|
};
|
|
457
457
|
/**
|
|
458
|
-
* View the content
|
|
458
|
+
* View the content items of the organization
|
|
459
459
|
*/
|
|
460
|
-
readonly
|
|
460
|
+
readonly CatalogManagementViewContentItems: {
|
|
461
461
|
readonly id: PermissionKey;
|
|
462
462
|
readonly category: "Catalog Management";
|
|
463
|
-
readonly subcategory: "Content
|
|
464
|
-
readonly function: "View Content
|
|
465
|
-
readonly description: "View the content
|
|
463
|
+
readonly subcategory: "Content Items";
|
|
464
|
+
readonly function: "View Content Items";
|
|
465
|
+
readonly description: "View the content items of the organization";
|
|
466
466
|
};
|
|
467
467
|
/**
|
|
468
|
-
* Create a content
|
|
468
|
+
* Create a content item in the organization
|
|
469
469
|
*/
|
|
470
|
-
readonly
|
|
470
|
+
readonly CatalogManagementCreateContentItem: {
|
|
471
471
|
readonly id: PermissionKey;
|
|
472
472
|
readonly category: "Catalog Management";
|
|
473
|
-
readonly subcategory: "Content
|
|
474
|
-
readonly function: "Create Content
|
|
475
|
-
readonly description: "Create a content
|
|
473
|
+
readonly subcategory: "Content Items";
|
|
474
|
+
readonly function: "Create Content Item";
|
|
475
|
+
readonly description: "Create a content item in the organization";
|
|
476
476
|
};
|
|
477
477
|
/**
|
|
478
|
-
* Edit a content
|
|
478
|
+
* Edit a content item of the organization
|
|
479
479
|
*/
|
|
480
|
-
readonly
|
|
480
|
+
readonly CatalogManagementEditContentItem: {
|
|
481
481
|
readonly id: PermissionKey;
|
|
482
482
|
readonly category: "Catalog Management";
|
|
483
|
-
readonly subcategory: "Content
|
|
484
|
-
readonly function: "Edit Content
|
|
485
|
-
readonly description: "Edit a content
|
|
483
|
+
readonly subcategory: "Content Items";
|
|
484
|
+
readonly function: "Edit Content Item";
|
|
485
|
+
readonly description: "Edit a content item of the organization";
|
|
486
486
|
};
|
|
487
487
|
/**
|
|
488
|
-
* Delete a content
|
|
488
|
+
* Delete a content item of the organization
|
|
489
489
|
*/
|
|
490
|
-
readonly
|
|
490
|
+
readonly CatalogManagementDeleteContentItem: {
|
|
491
491
|
readonly id: PermissionKey;
|
|
492
492
|
readonly category: "Catalog Management";
|
|
493
|
-
readonly subcategory: "Content
|
|
494
|
-
readonly function: "Delete Content
|
|
495
|
-
readonly description: "Delete a content
|
|
493
|
+
readonly subcategory: "Content Items";
|
|
494
|
+
readonly function: "Delete Content Item";
|
|
495
|
+
readonly description: "Delete a content item of the organization";
|
|
496
496
|
};
|
|
497
497
|
/**
|
|
498
498
|
* Invite any Meshery Cloud user, or all Meshery users, to work with you on a public design that control – including making changes and releasing new versions.
|
|
@@ -4759,21 +4759,21 @@ declare const PermissionKeys: {
|
|
|
4759
4759
|
*/
|
|
4760
4760
|
readonly CatalogManagementDeleteWasmFilter: PermissionKey;
|
|
4761
4761
|
/**
|
|
4762
|
-
* View the content
|
|
4762
|
+
* View the content items of the organization
|
|
4763
4763
|
*/
|
|
4764
|
-
readonly
|
|
4764
|
+
readonly CatalogManagementViewContentItems: PermissionKey;
|
|
4765
4765
|
/**
|
|
4766
|
-
* Create a content
|
|
4766
|
+
* Create a content item in the organization
|
|
4767
4767
|
*/
|
|
4768
|
-
readonly
|
|
4768
|
+
readonly CatalogManagementCreateContentItem: PermissionKey;
|
|
4769
4769
|
/**
|
|
4770
|
-
* Edit a content
|
|
4770
|
+
* Edit a content item of the organization
|
|
4771
4771
|
*/
|
|
4772
|
-
readonly
|
|
4772
|
+
readonly CatalogManagementEditContentItem: PermissionKey;
|
|
4773
4773
|
/**
|
|
4774
|
-
* Delete a content
|
|
4774
|
+
* Delete a content item of the organization
|
|
4775
4775
|
*/
|
|
4776
|
-
readonly
|
|
4776
|
+
readonly CatalogManagementDeleteContentItem: PermissionKey;
|
|
4777
4777
|
/**
|
|
4778
4778
|
* Invite any Meshery Cloud user, or all Meshery users, to work with you on a public design that control – including making changes and releasing new versions.
|
|
4779
4779
|
*/
|
package/dist/permissions.d.ts
CHANGED
|
@@ -23,7 +23,7 @@ interface Key {
|
|
|
23
23
|
/**
|
|
24
24
|
* Permissions Index ID used for this generated file.
|
|
25
25
|
*/
|
|
26
|
-
declare const PERMISSIONS_INDEX_ID: "
|
|
26
|
+
declare const PERMISSIONS_INDEX_ID: "1842d28fff5ae8af85366dd952d0d47c8e78c48d4bff56cf67fb856ac1b95463";
|
|
27
27
|
/**
|
|
28
28
|
* Creates a PermissionKey from a UUID string.
|
|
29
29
|
* @param uuid - The UUID string to convert
|
|
@@ -455,44 +455,44 @@ declare const Keys: {
|
|
|
455
455
|
readonly description: "Delete WASM filter permanently from catalog.";
|
|
456
456
|
};
|
|
457
457
|
/**
|
|
458
|
-
* View the content
|
|
458
|
+
* View the content items of the organization
|
|
459
459
|
*/
|
|
460
|
-
readonly
|
|
460
|
+
readonly CatalogManagementViewContentItems: {
|
|
461
461
|
readonly id: PermissionKey;
|
|
462
462
|
readonly category: "Catalog Management";
|
|
463
|
-
readonly subcategory: "Content
|
|
464
|
-
readonly function: "View Content
|
|
465
|
-
readonly description: "View the content
|
|
463
|
+
readonly subcategory: "Content Items";
|
|
464
|
+
readonly function: "View Content Items";
|
|
465
|
+
readonly description: "View the content items of the organization";
|
|
466
466
|
};
|
|
467
467
|
/**
|
|
468
|
-
* Create a content
|
|
468
|
+
* Create a content item in the organization
|
|
469
469
|
*/
|
|
470
|
-
readonly
|
|
470
|
+
readonly CatalogManagementCreateContentItem: {
|
|
471
471
|
readonly id: PermissionKey;
|
|
472
472
|
readonly category: "Catalog Management";
|
|
473
|
-
readonly subcategory: "Content
|
|
474
|
-
readonly function: "Create Content
|
|
475
|
-
readonly description: "Create a content
|
|
473
|
+
readonly subcategory: "Content Items";
|
|
474
|
+
readonly function: "Create Content Item";
|
|
475
|
+
readonly description: "Create a content item in the organization";
|
|
476
476
|
};
|
|
477
477
|
/**
|
|
478
|
-
* Edit a content
|
|
478
|
+
* Edit a content item of the organization
|
|
479
479
|
*/
|
|
480
|
-
readonly
|
|
480
|
+
readonly CatalogManagementEditContentItem: {
|
|
481
481
|
readonly id: PermissionKey;
|
|
482
482
|
readonly category: "Catalog Management";
|
|
483
|
-
readonly subcategory: "Content
|
|
484
|
-
readonly function: "Edit Content
|
|
485
|
-
readonly description: "Edit a content
|
|
483
|
+
readonly subcategory: "Content Items";
|
|
484
|
+
readonly function: "Edit Content Item";
|
|
485
|
+
readonly description: "Edit a content item of the organization";
|
|
486
486
|
};
|
|
487
487
|
/**
|
|
488
|
-
* Delete a content
|
|
488
|
+
* Delete a content item of the organization
|
|
489
489
|
*/
|
|
490
|
-
readonly
|
|
490
|
+
readonly CatalogManagementDeleteContentItem: {
|
|
491
491
|
readonly id: PermissionKey;
|
|
492
492
|
readonly category: "Catalog Management";
|
|
493
|
-
readonly subcategory: "Content
|
|
494
|
-
readonly function: "Delete Content
|
|
495
|
-
readonly description: "Delete a content
|
|
493
|
+
readonly subcategory: "Content Items";
|
|
494
|
+
readonly function: "Delete Content Item";
|
|
495
|
+
readonly description: "Delete a content item of the organization";
|
|
496
496
|
};
|
|
497
497
|
/**
|
|
498
498
|
* Invite any Meshery Cloud user, or all Meshery users, to work with you on a public design that control – including making changes and releasing new versions.
|
|
@@ -4759,21 +4759,21 @@ declare const PermissionKeys: {
|
|
|
4759
4759
|
*/
|
|
4760
4760
|
readonly CatalogManagementDeleteWasmFilter: PermissionKey;
|
|
4761
4761
|
/**
|
|
4762
|
-
* View the content
|
|
4762
|
+
* View the content items of the organization
|
|
4763
4763
|
*/
|
|
4764
|
-
readonly
|
|
4764
|
+
readonly CatalogManagementViewContentItems: PermissionKey;
|
|
4765
4765
|
/**
|
|
4766
|
-
* Create a content
|
|
4766
|
+
* Create a content item in the organization
|
|
4767
4767
|
*/
|
|
4768
|
-
readonly
|
|
4768
|
+
readonly CatalogManagementCreateContentItem: PermissionKey;
|
|
4769
4769
|
/**
|
|
4770
|
-
* Edit a content
|
|
4770
|
+
* Edit a content item of the organization
|
|
4771
4771
|
*/
|
|
4772
|
-
readonly
|
|
4772
|
+
readonly CatalogManagementEditContentItem: PermissionKey;
|
|
4773
4773
|
/**
|
|
4774
|
-
* Delete a content
|
|
4774
|
+
* Delete a content item of the organization
|
|
4775
4775
|
*/
|
|
4776
|
-
readonly
|
|
4776
|
+
readonly CatalogManagementDeleteContentItem: PermissionKey;
|
|
4777
4777
|
/**
|
|
4778
4778
|
* Invite any Meshery Cloud user, or all Meshery users, to work with you on a public design that control – including making changes and releasing new versions.
|
|
4779
4779
|
*/
|