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

Updated on 2025-12-12 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
codeartsdeploy:template:create	Grants permission to create templates in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:template:delete	Grants permission to delete templates in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:template:update	Grants permission to update templates in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:template:get	Grants permission to view template details in CodeArtsDeploy.	Read	-	-	-
codeartsdeploy:template:list	Grants permission to view template list in CodeArtsDeploy.	List	-	-	-
codeartsdeploy:application:create	Grants permission to create application in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:application:delete	Grants permission to delete applications in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:application:update	Grants permission to update applications in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:application:disable	Grants permission to disable applications in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:application:deploy	Grants permission to deploy applications in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:application:clone	Grants permission to clone applications in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:application:managePermission	Grants permission to modify applications permissions in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:application:get	Grants permission to view application details in CodeArtsDeploy.	Read	-	-	-
codeartsdeploy:application:list	Grants permission to view application list in CodeArtsDeploy.	List	-	-	-
codeartsdeploy:applicationGroup:manage	Grants permission to update application group in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:applicationGroup:list	Grants permission to view application group list in CodeArtsDeploy.	List	-	-	-
codeartsdeploy:environment:create	Grants permission to create environment in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:environment:delete	Grants permission to delete environment in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:environment:update	Grants permission to update environment in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:environment:get	Grants permission to view environment details in CodeArtsDeploy.	Read	-	-	-
codeartsdeploy:environment:list	Grants permission to view environment list in CodeArtsDeploy.	List	-	-	-
codeartsdeploy:environment:managePermission	Grants permission to modify environment permissions in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:resource:create	Grants permission to create resource in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:resource:delete	Grants permission to delete resource in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:resource:update	Grants permission to update resource in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:resource:addHost	Grants permission to add host to the resource in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:resource:copyHost	Grants permission to copy host to resource in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:resource:managePermission	Grants permission to modify resource permissions in CodeArtsDeploy.	Write	-	-	-
codeartsdeploy:resource:get	Grants permission to view resource in CodeArtsDeploy.	Read	-	-	-
codeartsdeploy:resource:list	Grants permission to view resource list in CodeArtsDeploy.	List	-	-	-

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
POST /v1/applications	codeartsdeploy:application:create	-
PUT /v1/applications	codeartsdeploy:application:update	-
DELETE /v1/applications/{app_id}	codeartsdeploy:application:delete	-
POST /v2/applications/batch-delete	codeartsdeploy:application:delete	-
GET /v1/applications/{app_id}/info	codeartsdeploy:application:get	-
POST /v1/applications/list	codeartsdeploy:application:list	-
POST /v1/applications/{app_id}/duplicate	codeartsdeploy:application:clone	-
GET /v1/applications/creatable	codeartsdeploy:application:list	-
GET /v1/applications/exist	codeartsdeploy:application:list	-
GET /v3/applications/permissions	codeartsdeploy:application:list	-
PUT /v3/applications/permissions	codeartsdeploy:application:managePermission	-
PUT /v3/applications/permission-level	codeartsdeploy:application:managePermission	-
GET /v2/tasks/{task_id}/state	codeartsdeploy:application:get	-
PUT /v1/applications/{app_id}/disable	codeartsdeploy:application:disable	-
POST /v2/tasks/template-task	codeartsdeploy:application:create	-
DELETE /v2/tasks/{task_id}	codeartsdeploy:application:delete	-
GET /v2/tasks/{task_id}	codeartsdeploy:application:get	-
GET /v2/{project_id}/task/{id}/history	codeartsdeploy:application:get	-
GET /v2/history/tasks/{task_id}/params	codeartsdeploy:application:get	-
GET /v2/{project_id}/metrics/success-rate	codeartsdeploy:application:list	-
POST /v2/{project_id}/tasks/metrics/success-rate	codeartsdeploy:application:list	-
POST /v2/tasks/{task_id}/start	codeartsdeploy:application:deploy	-
GET /v2/{project_id}/tasks/list	codeartsdeploy:application:list	-
POST /v1/projects/{project_id}/applications/groups	codeartsdeploy:applicationGroup:manage	-
PUT /v1/projects/{project_id}/applications/groups/move	codeartsdeploy:applicationGroup:manage	-
PUT /v1/projects/{project_id}/applications/groups/swap	codeartsdeploy:applicationGroup:manage	-
DELETE /v1/projects/{project_id}/applications/groups/{group_id}	codeartsdeploy:applicationGroup:manage	-
PUT /v1/projects/{project_id}/applications/groups/{group_id}	codeartsdeploy:applicationGroup:manage	-
GET /v1/projects/{project_id}/applications/groups	codeartsdeploy:applicationGroup:list	-
POST /v2/host-groups/{group_id}/hosts	codeartsdeploy:resource:addHost	-
GET /v2/host-groups/{group_id}/hosts	codeartsdeploy:resource:get	-
PUT /v1/resources/host-groups/{group_id}/hosts/{host_id}	codeartsdeploy:resource:update	-
DELETE /v1/resources/host-groups/{group_id}/hosts/{host_id}	codeartsdeploy:resource:delete	-
GET /v1/resources/host-groups/{group_id}/hosts/{host_id}	codeartsdeploy:resource:get	-
GET /v2/host-groups/{group_id}	codeartsdeploy:resource:get	-
DELETE /v2/host-groups/{group_id}	codeartsdeploy:resource:delete	-
PUT /v2/host-groups/{group_id}	codeartsdeploy:resource:update	-
GET /v1/resources/host-groups/{group_id}/hosts	codeartsdeploy:resource:get	-
GET /v2/host-groups/{group_id}/permissions	codeartsdeploy:resource:get	-
PUT /v2/host-groups/{group_id}/permissions	codeartsdeploy:resource:managePermission	-
GET /v1/resources/host-groups/{group_id}/environments/infos	codeartsdeploy:resource:list	-
POST /v1/resources/host-groups/{group_id}/hosts	codeartsdeploy:resource:addHost	-
POST /v2/host-groups	codeartsdeploy:resource:create	-
GET /v2/host-groups	codeartsdeploy:resource:list	-
POST /v1/resources/host-groups/{group_id}/hosts/batch-delete	codeartsdeploy:resource:delete	-
POST /v1/resources/host-groups/{group_id}/hosts/replication	codeartsdeploy:resource:copyHost	-
GET /v1/resources/host-groups/{group_id}	codeartsdeploy:resource:get	-
POST /v1/resources/host-groups	codeartsdeploy:resource:create	-
GET /v1/resources/host-groups	codeartsdeploy:resource:list	-
GET /v1/host-groups/creatable/{project_id}/permissions	codeartsdeploy:resource:list	-
PUT /v1/resources/host-groups/{group_id}	codeartsdeploy:resource:update	-
DELETE /v1/resources/host-groups/{group_id}	codeartsdeploy:resource:delete	-
DELETE /v2/host-groups/{group_id}/hosts/{host_id}	codeartsdeploy:resource:delete	-
PUT /v2/host-groups/{group_id}/hosts/{host_id}	codeartsdeploy:resource:update	-
GET /v2/host-groups/{group_id}/hosts/{host_id}	codeartsdeploy:resource:get	-
DELETE /v1/applications/{application_id}/environments/{environment_id}/{host_id}	codeartsdeploy:environment:delete	-
DELETE /v1/applications/{application_id}/environments/{environment_id}	codeartsdeploy:environment:delete	-
GET /v1/applications/{application_id}/environments/{environment_id}	codeartsdeploy:environment:get	-
PUT /v1/applications/{application_id}/environments/{environment_id}	codeartsdeploy:environment:update	-
GET /v1/applications/{application_id}/host-groups/base/infos	codeartsdeploy:environment:list	-
POST /v1/applications/{application_id}/environments	codeartsdeploy:environment:create	-
GET /v1/applications/{application_id}/environments	codeartsdeploy:environment:list	-
POST /v1/applications/{application_id}/environments/{environment_id}/hosts/import	codeartsdeploy:environment:update	-
GET /v1/applications/{application_id}/environments/{environment_id}/hosts	codeartsdeploy:environment:get	-

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.

Previous topic: Example 3: Querying the Host List of a Specified Host Cluster

Next topic: Appendixes