Before You Start

Welcome to CodeArts Pipeline. CodeArts Pipeline provides visual, customizable pipelines to shorten the delivery period and improve efficiency.

This document describes how to use APIs to perform operations on pipelines, such as starting and stopping pipelines. For details about all supported operations, see API Overview.

Before calling CodeArts Pipeline APIs, ensure that you are familiar with CodeArts Pipeline concepts. For details, see Service Overview.

CodeArts Pipeline supports Representational State Transfer (REST) APIs that can be called using HTTPS. For details, see Calling APIs.

Endpoints

An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For the endpoints of all services, see Regions and Endpoints.

Table 1 lists the CodeArts Pipeline endpoints.

**Table 1** CodeArts Pipeline endpoints
Region Name	Region	Endpoint	Protocol
LA-Mexico City2	la-north-2	devcloud.la-north-2.myhuaweicloud.com	HTTPS
LA-Sao Paulo1	sa-brazil-1	devcloud.sa-brazil-1.myhuaweicloud.com	HTTPS
AP-Singapore	ap-southeast-3	devcloud.ap-southeast-3.myhuaweicloud.com	HTTPS
TR-Istanbul	tr-west-1	pipeline-external.tr-west-1.myhuaweicloud.com	HTTPS
LA-Santiago	la-south-2	pipeline-external.la-south-2.myhuaweicloud.com	HTTPS

Concepts

Account
An account is created upon successful registration with Huawei Cloud. The account has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. The account is a payment entity and should not be used directly to perform routine management. For security purposes, create IAM users and grant them permissions for routine management.
User
An identity and access management (IAM) user is created using an account to use cloud services. Each IAM user has their own identity credentials (password and access keys).

An IAM user can view the account ID and user ID on the My Credentials page of the console. The account, username, and password are required for API authentication.
Region
Regions are divided based on geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region.

Regions are classified into universal regions and dedicated regions.
- A universal region provides universal cloud services for common tenants.
- A dedicated region provides particular services for specific tenants.
For details, see Region and AZ.
Availability zone
An availability zone (AZ) contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to allow you to build cross-AZ high-availability (HA) systems.
Project
Projects group and isolate resources (including compute, storage, and network resources) across physical regions. A default project is provided for each region, and subprojects can be created under each default project. Users can be granted permissions to access all resources in a specific project.

For more refined access control, create subprojects under a project and purchase resources in the subprojects. Then you can assign required permissions for users to access only resources in specific subprojects.
Enterprise project
An enterprise project groups and manages enterprise resources in a logically isolated manner. It contains resources in multiple regions, and allows resources to be added or removed.

For details about how to obtain enterprise project IDs and features, see Enterprise Management User Guide.