Help Center/ CodeArts Artifact/ API Reference/ Appendix/ Actions Supported by Identity Policy-based Authorization

Updated on 2026-01-22 GMT+08:00

View PDF

Actions Supported by Identity Policy-based Authorization

IAM provides system-defined identity policies to define typical cloud service permissions. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service also provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see How IAM Is Different from Organizations for Access Control?.

This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.

For details about how to use these elements to edit an IAM custom identity policy, see Creating a Custom Identity Policy.
For details about how to use these elements to edit a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an identity policy.

The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
The Resource Type column indicates whether the action supports resource-level permissions.
- You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your identity policy statements.
- Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.
For details about the resource types defined by deployman, see Resources.
The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
- If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column is empty (-) for an action, the action does not support any condition keys.
For details about the condition keys defined by deployman, see Conditions.
The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for deployman.

**Table 1** Actions supported by deployman
Action	Description	Access Level	Resource Type (*: required)	Condition Key	Alias
codeartsartifact:repository:download	Grants permission to return artifact and metadata from repository.	Read	-	-	-
codeartsartifact:repository:upload	Grants permission to upload artifact and metadata to repository.	Write	-	-	-
codeartsartifact:repository:deleteFromRepository	Grants permission to delete artifact.	Write	-	-	-
codeartsartifact:releaseRepo:download	Grants permission to download package and metadata from releaseRepo.	Read	-	-	-
codeartsartifact:releaseRepo:read	Grants permission to return package info and metadata from releaseRepo.	Read	-	-	-
codeartsartifact:releaseRepo:upload	Grants permission to upload package and metadata to releaseRepo.	Write	-	-	-
codeartsartifact:releaseRepo:createFolder	Grants permission to create folder in releaseRepo.	Write	-	-	-
codeartsartifact:releaseRepo:editTestPackage	Grants permission to edit test package in releaseRepo.	Write	-	-	-
codeartsartifact:releaseRepo:deleteOrRestorePackage	Grants permission to delete or restore package in releaseRepo.	Write	-	-	-
codeartsartifact:releaseRepo:restoreTrash	Grants permission to restore trash in releaseRepo.	Write	-	-	-
codeartsartifact:releaseRepo:clearTrash	Grants permission to clear trash in releaseRepo.	Write	-	-	-
codeartsartifact:releaseRepo:changePackageStatus	Grants permission to change package status in releaseRepo.	Write	-	-	-
codeartsartifact:releaseRepo:getProjectInfo	Grants permission to get project information in releaseRepo.	Read	-	-	-
codeartsartifact:releaseRepo:updateProjectConfiguration	Grants permission to update project configuration in releaseRepo.	Write	-	-	-
codeartsartifact:proxy:list	Grants permission to list net proxy.	List	-	-	-
codeartsartifact:proxy:create	Grants permission to create net proxy.	Write	-	-	-
codeartsartifact:proxy:update	Grants permission to update net proxy.	Write	-	-	-
codeartsartifact:proxy:delete	Grants permission to delete net proxy.	Write	-	-	-
codeartsartifact:repository:create	Grants permission to create repository.	Write	-	-	-
codeartsartifact:repository:edit	Grants permission to edit repository.	Write	-	-	-
codeartsartifact:repository:delete	Grants permission to delete repository.	Write	-	-	-
codeartsartifact:repository:list	Grants permission to list repositories information.	List	-	-	-
codeartsartifact:repository:read	Grants permission to return repository information.	Read	-	-	-
codeartsartifact:repository:restore	Grants permission to restore repository.	Write	-	-	-
codeartsartifact:repository:completelyDelete	Grants permission to completely delete repository.	Write	-	-	-
codeartsartifact:repository:restoreAll	Grants permission to restore all trash.	Write	-	-	-
codeartsartifact:repository:clearAll	Grants permission to clear all trash.	Write	-	-	-
codeartsartifact:repository:listUsers	Grants permission to list users.	List	-	-	-
codeartsartifact:repository:readUser	Grants permission to return user information.	Read	-	-	-
codeartsartifact:repository:updateUser	Grants permission to update user in repository.	Write	-	-	-
codeartsartifact:repository:deleteUser	Grants permission to delete user in repository.	Write	-	-	-
codeartsartifact:repository:getSetting	Grants permission to get setting in repository.	Read	-	-	-
codeartsartifact:repository:resetPassword	Grants permission to reset password in repository.	Write	-	-	-
codeartsartifact:repository:getVersionInfo	Grants permission to get version information in repository.	Read	-	-	-
codeartsartifact:securityTask:create	Grants permission to create secguard task.	Write	-	-	-
codeartsartifact:securityTask:delete	Grants permission to delete secguard task.	Write	-	-	-
codeartsartifact:securityTask:list	Grants permission to list secguard task.	List	-	-	-
codeartsartifact:securityTask:read	Grants permission to return secguard task information.	Read	-	-	-
codeartsartifact:securityTask:update	Grants permission to update secguard task.	Write	-	-	-
codeartsartifact::getAccountInfo	Grants permission to get account info.	Read	-	-	-
codeartsartifact::updateAccountConfiguration	Grants permission to update account configuration.	Write	-	-	-

Each API of deployman usually supports one or more actions. Table 2 lists the supported actions and dependencies.

**Table 2** Actions and dependencies supported by deployman APIs
API	Action	Dependencies
GET /devreposerver/v2/release/{project_id}/files	codeartsartifact:releaseRepo:read	-
GET /v2/{project_id}/release/files	codeartsartifact:releaseRepo:read	-
PUT /v5/trashes	codeartsartifact:repository:restore	-
DELETE /v5/trashes	codeartsartifact:repository:completelyDelete	-
POST /v5/maven/repositories	codeartsartifact:repository:create	-
GET /v5/maven/repository/list	codeartsartifact:repository:list	-
PUT /v5/repositories/tab/{tab_id}	codeartsartifact:repository:edit	-
GET /v5/repositories/{repo_id}	codeartsartifact:repository:read	-
POST /v5/repositories	codeartsartifact:repository:create	-
DELETE /v5/repositories	codeartsartifact:repository:delete	-
GET /v5/storage	codeartsartifact:repository:list	-
GET /v5/maven/info	codeartsartifact:repository:list	-
POST /v5/maven/project/repository	codeartsartifact:repository:create	-
GET /v5/search/checksum	codeartsartifact:repository:list	-
POST /v5/tree/repos/artifacts	codeartsartifact:repository:list	-
POST /v5/maven/users/me	codeartsartifact:repository:resetPassword	-
GET /v5/{tenant_id}/{project_id}/{repo_name}/file-tree	codeartsartifact:repository:read	-
GET /v5/{tenant_id}/{project_id}/{repo_name}/file-detail	codeartsartifact:repository:read	-
GET /v5/{tenant_id}/{project_id}/repositories	codeartsartifact:repository:list	-
GET /v5/{tenant_id}/{project_id}/{module}/{repo}/audit	codeartsartifact:repository:read	-
GET /v5/{tenant_id}/{project_id}/{repo_id}/repositories	codeartsartifact:repository:read	-
GET /v5/{tenant_id}/{project_id}/storageinfo/statistic	codeartsartifact:repository:read	-
POST /v5/attention	codeartsartifact:repository:list	-
GET /v5/attention/artifacts	codeartsartifact:repository:list	-
POST /v5/artifact/	codeartsartifact:repository:create	-
PUT /v5/artifact/	codeartsartifact:repository:edit	-
DELETE /v5/file	codeartsartifact:repository:deleteFromRepository	-
GET /v3/user/{project_id}/privileges	codeartsartifact:repository:list	-
GET /v5/maven/list	codeartsartifact:repository:list	-
GET /v5/projects/{project_id}/users	codeartsartifact:repository:listUsers	-
GET /v5/repositories/proxy	codeartsartifact:repository:read	-
GET /v5/tree/net/proxy	codeartsartifact:proxy:list	-
GET /v5/domain/ipconfig	codeartsartifact::getAccountInfo	-
GET /v5/sec-guard/task/list	codeartsartifact:securityTask:list	-
GET /v5/repositories/users	codeartsartifact:repository:listUsers	-
GET /v5/data/package	codeartsartifact:releaseRepo:read	-
GET /v5/data/package/info	codeartsartifact:releaseRepo:read	-
GET /v5/release/{project_id}/auto-deletion/settings	codeartsartifact:releaseRepo:getProjectInfo	-
DELETE /v5/files/compeletion	codeartsartifact:releaseRepo:deleteOrRestorePackage	-
GET /v5/files/archives	codeartsartifact:releaseRepo:read	-
GET /v5/project-role/permissions	codeartsartifact:releaseRepo:getProjectInfo	-
GET /v5/capacity-notice/settings	codeartsartifact::getAccountInfo	-
POST /v5/files/list	codeartsartifact:releaseRepo:read	-
GET /v5/{project_id}/files/version/count	codeartsartifact:releaseRepo:read	-
GET /v5/{project_id}/files/version	codeartsartifact:releaseRepo:read	-
GET /v5/files/{id}/info	codeartsartifact:releaseRepo:read	-
GET /v5/files/info	codeartsartifact:releaseRepo:read	-
GET /v5/storage	codeartsartifact::getAccountInfo	-
GET /v5/{project_id}/storage	codeartsartifact:releaseRepo:getProjectInfo	-

Resources

deployman does not support resource-level authorization. To allow access to deployman, use a wildcard (*) in the Resource element of the identity policy, indicating that the identity policy will be applied to all resources.

Conditions

deployman does not support service-specific condition keys in identity policies. It can only use global condition keys applicable to all services. For details, see Global Condition Keys.

Parent topic: Appendix

Previous topic: Obtaining an Account ID

Next topic: Change History