CodeArts
CodeArts
- Service Overview
- Billing
- Getting Started
-
User Guide
- Preparations
- CodeArts Req
- CodeArts Repo
- CodeArts Pipeline
- CodeArts Check
- CodeArts Build
- CodeArts Artifact
- CodeArts Deploy
- CodeArts TestPlan
- CodeArts PerfTest
-
Best Practices
- Best Practices Summary
-
Using CodeArts to Manage an e-Mall Development Project
- Overview
- Resource Planning
- Process
-
Implementation Procedure
- Preparation
- Step 1: Managing Project Plans
- Step 2: Managing Project Configurations
- Step 3: Writing Code
- Step 4: Checking Code
- Step 5: Building an Application
- Step 6: Deploying an Application (CCE)
- Step 6: Deploying an Application (ECS)
- Step 7: Managing Project Tests
- Step 8: Configuring a Pipeline for Continuous Delivery
- Releasing Resources
-
FAQs
-
General
- How Do I Collect or Archive Project Information Locally After a CodeArts Project Is Complete?
- Why Can't an IAM User View Any CodeArts Projects After Login?
- How Do I View All CodeArts Projects and Members Under My Account as Administrator?
- Will the Tasks Created by a Project Member Be Deleted After the Member Leaves the Project?
- Will a New User with the Same Name as a Deleted User Inherit Their Permissions and Tasks?
- CodeArts Req
- CodeArts Repo
- CodeArts Pipeline
- CodeArts Check
- CodeArts Build
- CodeArts Artifact
- CodeArts Deploy
- CodeArts TestPlan
- CodeArts PerfTest
-
General
- Videos
- General Reference
On this page
Show all
Help Center/
CodeArts/
User Guide/
Preparations/
Configuring CodeArts Console Permissions/
Custom Policies
Copied.
Custom Policies
You can customize policies to supplement system-defined policies of CodeArts.
You can create custom policies using one of the following methods:
- Visual editor: Select cloud services, actions, resources, and request conditions. You do not need to have knowledge of the policy syntax.
- JSON: Create a policy in the JSON format from scratch or based on an existing policy.
For details, see Creating a Custom Policy. This section provides examples of common custom policies in CodeArts.
CodeArts Custom Policy Examples
- Example 1: Authorize users to purchase CodeArts on the console
{ "Version": "1.1", "Statement": [ { "Effect": "Allow", "Action": [ " devcloud:monthlyPackage:subscribe " ] } ] }
- Example 2: Define actions for multiple services in a policy
A custom policy can contain the actions of multiple services that are of the global or project-level type. The following is an example policy containing actions of multiple services:
{ "Version": "1.1", "Statement": [ { "Action": [ "devcloud:*:listResourceDetail", "ecs:cloudServers:delete" ], "Effect": "Allow" } ] }
Parent topic: Configuring CodeArts Console Permissions
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot