Help Center/ System Permissions/ User Guide/ Identity Policy–based Authorization/ Developer Services/ CodeArts Pipeline
Updated on 2025-11-06 GMT+08:00
View PDF
Share

CodeArts Pipeline

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.

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 CodeartsPipeline, 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 CodeartsPipeline, 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 CodeartsPipeline.

Table 1 Actions supported by CodeartsPipeline

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

codeartspipeline:pipelinetemplate:create

Grants permission to create a pipeline template.

Write

-

-

-

codeartspipeline:pipelinetemplate:update

Grants permission to update a pipeline template.

Write

-

-
  • cloudpipeline:pipelinetemplate:update

codeartspipeline:pipelinetemplate:delete

Grants permission to delete a pipeline template.

Write

-

-
  • cloudpipeline:pipelinetemplate:update

codeartspipeline:pipelinetemplate:get

Grants permission to view a pipeline template.

Read

-

-

-

codeartspipeline:pipelinetemplate:list

Grants permission to view the pipeline template list.

List

-

-

-

codeartspipeline:rule:create

Grants permission to create a rule.

Write

-

-
  • cloudpipeline:rule:update

codeartspipeline:rule:update

Grants permission to update a rule.

Write

-

-
  • cloudpipeline:rule:update

codeartspipeline:rule:delete

Grants permission to delete a rule.

Write

-

-
  • cloudpipeline:rule:update

codeartspipeline:rule:get

Grants permission to view a rule.

Read

-

-

-

codeartspipeline:rule:list

Grants permission to view the rule list.

List

-

-

-

codeartspipeline:strategy:create

Grants permission to create a strategy.

Write

-

-
  • cloudpipeline:ruletemplate:update

codeartspipeline:strategy:update

Grants permission to update a strategy.

Write

-

-
  • cloudpipeline:ruletemplate:update

codeartspipeline:strategy:delete

Grants permission to delete a strategy.

Write

-

-
  • cloudpipeline:ruletemplate:update

codeartspipeline:strategy:get

Grants permission to view a strategy.

Read

-

-

-

codeartspipeline:strategy:list

Grants permission to view the strategy list.

List

-

-

-

codeartspipeline:extension:create

Grants permission to create an extension plugin.

Write

-

-
  • cloudpipeline:extensions:update

codeartspipeline:extension:update

Grants permission to update an extension plugin.

Write

-

-
  • cloudpipeline:extensions:update

codeartspipeline:extension:delete

Grants permission to delete an extension plugin.

Write

-

-
  • cloudpipeline:extensions:update

codeartspipeline:extension:get

Grants permission to view an extension plugin.

Read

-

-

-

codeartspipeline:extension:list

Grants permission to list all pipeline extensions.

List

-

-

-

Resources

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

Conditions

CodeartsPipeline 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: Developer Services