@pulumi/artifactory 6.1.4 → 6.1.5

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@pulumi/artifactory",
-    "version": "v6.1.4",
+    "version": "v6.1.5",
     "description": "A Pulumi package for creating and managing artifactory cloud resources.",
     "keywords": [
         "pulumi",

package/scopedToken.d.ts

@@ -144,16 +144,16 @@ export declare class ScopedToken extends pulumi.CustomResource {
      * supported scopes include: * `applied-permissions/user` - provides user access. If left at the default setting, the token
      * will be created with the user-identity scope, which allows users to identify themselves in the Platform but does not
      * grant any specific access permissions.* `applied-permissions/admin` - the scope assigned to admin users.*
-     * `applied-permissions/groups` - the group to which permissions are assigned by group name (use username to indicate the
-     * group name)* `system:metrics:r` - for getting the service metrics* `system:livelogs:r` - for getting the service
-     * livelogsr. The scope to assign to the token should be provided as a list of scope tokens, limited to 500 characters in
-     * total. Resource Permissions From Artifactory 7.38.x, resource permissions scoped tokens are also supported in the REST
-     * API. A permission can be represented as a scope token string in the following format:
-     * `<resource-type>:<target>[/<sub-resource>]:<actions>` Where: `<resource-type>` - one of the permission resource types,
-     * from a predefined closed list. Currently, the only resource type that is supported is the artifact resource type.
-     * `<target>` - the target resource, can be exact name or a pattern `<sub-resource>` - optional, the target sub-resource,
-     * can be exact name or a pattern `<actions>` - comma-separated list of action acronyms.The actions allowed are `r`, `w`,
-     * `d`, `a`, `m`, `x`, `s`, or any combination of these actions. To allow all actions - use `*` Examples:
+     * `applied-permissions/groups` - this scope assigns permissions to groups using the following format:
+     * applied-permissions/groups:<group-name>[,<group-name>...]* `system:metrics:r` - for getting the service metrics*
+     * `system:livelogs:r` - for getting the service livelogsr. The scope to assign to the token should be provided as a list
+     * of scope tokens, limited to 500 characters in total. Resource Permissions From Artifactory 7.38.x, resource permissions
+     * scoped tokens are also supported in the REST API. A permission can be represented as a scope token string in the
+     * following format: `<resource-type>:<target>[/<sub-resource>]:<actions>` Where: `<resource-type>` - one of the permission
+     * resource types, from a predefined closed list. Currently, the only resource type that is supported is the artifact
+     * resource type. `<target>` - the target resource, can be exact name or a pattern `<sub-resource>` - optional, the target
+     * sub-resource, can be exact name or a pattern `<actions>` - comma-separated list of action acronyms.The actions allowed
+     * are `r`, `w`, `d`, `a`, `m`, `x`, `s`, or any combination of these actions. To allow all actions - use `*` Examples:
      * `["applied-permissions/user", "artifact:generic-local:r"]` `["applied-permissions/group",
      * "artifact:generic-local/path:*"]` `["applied-permissions/admin", "system:metrics:r", "artifact:generic-local:*"]`
      */
@@ -254,16 +254,16 @@ export interface ScopedTokenState {
      * supported scopes include: * `applied-permissions/user` - provides user access. If left at the default setting, the token
      * will be created with the user-identity scope, which allows users to identify themselves in the Platform but does not
      * grant any specific access permissions.* `applied-permissions/admin` - the scope assigned to admin users.*
-     * `applied-permissions/groups` - the group to which permissions are assigned by group name (use username to indicate the
-     * group name)* `system:metrics:r` - for getting the service metrics* `system:livelogs:r` - for getting the service
-     * livelogsr. The scope to assign to the token should be provided as a list of scope tokens, limited to 500 characters in
-     * total. Resource Permissions From Artifactory 7.38.x, resource permissions scoped tokens are also supported in the REST
-     * API. A permission can be represented as a scope token string in the following format:
-     * `<resource-type>:<target>[/<sub-resource>]:<actions>` Where: `<resource-type>` - one of the permission resource types,
-     * from a predefined closed list. Currently, the only resource type that is supported is the artifact resource type.
-     * `<target>` - the target resource, can be exact name or a pattern `<sub-resource>` - optional, the target sub-resource,
-     * can be exact name or a pattern `<actions>` - comma-separated list of action acronyms.The actions allowed are `r`, `w`,
-     * `d`, `a`, `m`, `x`, `s`, or any combination of these actions. To allow all actions - use `*` Examples:
+     * `applied-permissions/groups` - this scope assigns permissions to groups using the following format:
+     * applied-permissions/groups:<group-name>[,<group-name>...]* `system:metrics:r` - for getting the service metrics*
+     * `system:livelogs:r` - for getting the service livelogsr. The scope to assign to the token should be provided as a list
+     * of scope tokens, limited to 500 characters in total. Resource Permissions From Artifactory 7.38.x, resource permissions
+     * scoped tokens are also supported in the REST API. A permission can be represented as a scope token string in the
+     * following format: `<resource-type>:<target>[/<sub-resource>]:<actions>` Where: `<resource-type>` - one of the permission
+     * resource types, from a predefined closed list. Currently, the only resource type that is supported is the artifact
+     * resource type. `<target>` - the target resource, can be exact name or a pattern `<sub-resource>` - optional, the target
+     * sub-resource, can be exact name or a pattern `<actions>` - comma-separated list of action acronyms.The actions allowed
+     * are `r`, `w`, `d`, `a`, `m`, `x`, `s`, or any combination of these actions. To allow all actions - use `*` Examples:
      * `["applied-permissions/user", "artifact:generic-local:r"]` `["applied-permissions/group",
      * "artifact:generic-local/path:*"]` `["applied-permissions/admin", "system:metrics:r", "artifact:generic-local:*"]`
      */
@@ -332,16 +332,16 @@ export interface ScopedTokenArgs {
      * supported scopes include: * `applied-permissions/user` - provides user access. If left at the default setting, the token
      * will be created with the user-identity scope, which allows users to identify themselves in the Platform but does not
      * grant any specific access permissions.* `applied-permissions/admin` - the scope assigned to admin users.*
-     * `applied-permissions/groups` - the group to which permissions are assigned by group name (use username to indicate the
-     * group name)* `system:metrics:r` - for getting the service metrics* `system:livelogs:r` - for getting the service
-     * livelogsr. The scope to assign to the token should be provided as a list of scope tokens, limited to 500 characters in
-     * total. Resource Permissions From Artifactory 7.38.x, resource permissions scoped tokens are also supported in the REST
-     * API. A permission can be represented as a scope token string in the following format:
-     * `<resource-type>:<target>[/<sub-resource>]:<actions>` Where: `<resource-type>` - one of the permission resource types,
-     * from a predefined closed list. Currently, the only resource type that is supported is the artifact resource type.
-     * `<target>` - the target resource, can be exact name or a pattern `<sub-resource>` - optional, the target sub-resource,
-     * can be exact name or a pattern `<actions>` - comma-separated list of action acronyms.The actions allowed are `r`, `w`,
-     * `d`, `a`, `m`, `x`, `s`, or any combination of these actions. To allow all actions - use `*` Examples:
+     * `applied-permissions/groups` - this scope assigns permissions to groups using the following format:
+     * applied-permissions/groups:<group-name>[,<group-name>...]* `system:metrics:r` - for getting the service metrics*
+     * `system:livelogs:r` - for getting the service livelogsr. The scope to assign to the token should be provided as a list
+     * of scope tokens, limited to 500 characters in total. Resource Permissions From Artifactory 7.38.x, resource permissions
+     * scoped tokens are also supported in the REST API. A permission can be represented as a scope token string in the
+     * following format: `<resource-type>:<target>[/<sub-resource>]:<actions>` Where: `<resource-type>` - one of the permission
+     * resource types, from a predefined closed list. Currently, the only resource type that is supported is the artifact
+     * resource type. `<target>` - the target resource, can be exact name or a pattern `<sub-resource>` - optional, the target
+     * sub-resource, can be exact name or a pattern `<actions>` - comma-separated list of action acronyms.The actions allowed
+     * are `r`, `w`, `d`, `a`, `m`, `x`, `s`, or any combination of these actions. To allow all actions - use `*` Examples:
      * `["applied-permissions/user", "artifact:generic-local:r"]` `["applied-permissions/group",
      * "artifact:generic-local/path:*"]` `["applied-permissions/admin", "system:metrics:r", "artifact:generic-local:*"]`
      */