API Overview
Type |
Subtype |
Description |
---|---|---|
Application management V3 APIs |
APIs related to environments. An environment is a collection of basic compute (such as CCE and ECS), network (such as ELB and EIP), and middleware (such as DCS and RDS) resources, used for component deployment and running. ServiceStage combines multiple basic resources into an environment, including development, test, pre-production, and production environments. Managing resources and deploying components by environment simplifies O&M management. |
|
APIs related to applications. An application is a service system with functions and consists of one or more components. |
||
APIs related to components. A component is a service feature implementation of an application. It is carried by code or software packages and can be independently deployed and run in an environment. |
||
APIs related to configurations. In ServiceStage, a configuration is a file. By creating a unified configuration file, you can fill the system variables (such as the IP address, port number, database address, and application name associated with the environment) of the environment and application in the configuration to generate a configuration file. When a component is associated with a configuration file for deployment, the system variables are automatically replaced with the actual value. This implements multi-environment use with one-time configuration through file mounting. |
||
APIs related to the technology stack. A technology stack includes the operating system, framework, and runtime system on which component running depends. It consists of attributes such as the technology stack name, type, status, and version. The version number complies with the semantic versioning specifications. ServiceStage provides and manages the stack lifecycle. You only need to focus on service development to improve application hosting experience. |
||
APIs related to deployment jobs. |
||
APIs related to add-on management. |
||
Git repository access APIs |
APIs related to Git repository authorization, namespaces, projects, branches, tags, commits, hooks, repository file directories, and contents. |
|
CSE APIs |
APIs related to configuration import to and export from the configuration management center. |
|
APIs related to exclusive microservice engine creation, query, and deletion. |
||
ServiceComb APIs |
APIs related to microservice identity authentication. |
|
APIs related to microservice management. |
||
APIs related to microservice contract query and upload. |
||
APIs related to microservice instance registry and heartbeat reporting. |
||
APIs related to microservice dependency query. |
||
APIs related to configuration management of the configuration center. |
Environment APIs
API |
Description |
---|---|
Create an environment. |
|
Obtain all environments. |
|
Delete an environment based on the environment ID. |
|
Modify an environment based on the environment ID. |
|
Obtain environment details based on the environment ID. |
|
Modifying an Environment Resource Based on the Environment ID |
Modify an environment resource based on environment ID. |
Enabling an Environment Resource Based on the Environment ID |
Query an environment resource based on environment ID. |
Query a managed resource based on the environment ID. |
|
Query a created resource based on the environment ID. |
|
Add an environment resource based on the environment ID. |
|
Updating an Environment Resource Based on the Environment ID |
Update an environment resource based on the environment ID. |
Deleting an Environment Resource Based on the Environment ID |
Delete an environment resource based on the environment ID. |
Querying Resource Enabling Records Based on the Environment ID |
Query resource enabling records based on the environment ID. |
Querying the Details of a Resource Enabling Record Based on the Environment ID |
Query the details of a resource enabling record based on the environment ID. |
Querying the Events of a Resource Enabling Record Based on the Environment ID |
Query the events of a resource enabling record based on the environment ID. |
Application APIs
API |
Description |
---|---|
Create an application. |
|
Obtain all applications. |
|
Modifying Application Information Based on the Application ID |
Modify application information based on the application ID. |
Delete an application based on the application ID. |
|
Obtain application details based on the application ID. |
|
Obtaining Application Configurations Based on the Application ID |
Obtain application configurations based on the application ID. |
Modifying Application Configurations Based on the Application ID |
Modify application configurations based on the application ID. |
Deleting Application Configurations Based on the Application ID |
Delete application configurations based on the application ID. |
Component APIs
API |
Description |
---|---|
Create an application component. |
|
Obtain all components of an application. |
|
Obtain all components. |
|
Modify component information based on the component ID. |
|
Delete a component based on the component ID. |
|
Obtain component information based on the component ID. |
|
Deliver a component action based on the component ID. |
|
Obtain records based on the component ID. |
|
Refresh the component status and access mode based on the component ID. |
|
Obtain information about the application, environment, and enterprise project to which all components belong. |
Technology Stack APIs
API |
Description |
---|---|
Query technology stack information. |
|
Obtain the built-in basic images used for building ServiceStage technology stacks. |
|
Create a custom technology stack. |
|
Querying a Technology Stack Based on the Technology Stack ID |
Query a technology stack based on the technology stack ID. |
Modifying a Technology Stack Based on the Technology Stack ID |
Modify a technology stack based on the technology stack ID. |
Deleting a Technology Stack Based on the Technology Stack ID |
Delete a technology stack based on the technology stack ID. |
Release or cancel the release of a technology stack. |
Configuration Management APIs
API |
Description |
---|---|
Create a configuration group to manage configuration files. |
|
Obtain all created configuration groups. |
|
Create a configuration file. |
|
Import a configuration file in .zip format. |
|
Obtain the configuration file information. |
|
Obtaining Configuration File Information Based on the Configuration File ID |
Obtain the details about a configuration file based on the configuration file ID. |
Deleting a Configuration File Based on the Configuration File ID |
Delete a configuration file based on the configuration file ID. |
Modifying a Configuration File Based on the Configuration File ID |
Modify a configuration file based on the configuration file ID. |
Obtaining the Configuration File Record Based on the Configuration File ID |
Obtain the configuration file record based on the configuration file ID. |
Obtaining the Configuration File Record Information Based on the Record ID |
Obtain the configuration file record information based on the record ID. |
Delete a configuration file record based on the record ID. |
|
Obtain the configuration group details based on the group ID. |
|
Delete a configuration group based on the group ID. |
Add-on Management APIs
API |
Description |
---|---|
Create an add-on. |
|
Query the add-on list in an environment. |
|
Query the add-on metadata in an environment. |
|
Query details about an add-on in an environment. |
|
Deliver an add-on job based on the add-on ID. |
|
Delete an add-on based on the add-on ID. |
Git Repository Access APIs
API |
Description |
---|---|
Obtain the Git repository authorization list. |
|
Obtain an authorization redirection URL. |
|
Create OAuth authorization. |
|
Create private token authorization. |
|
Create password authorization for a Git repository. |
|
Delete repository authorization based on the name. |
|
Obtain namespaces of a repository. |
|
Obtain repository information based on the clone URL. |
|
Obtain all projects in a namespace. |
|
Create a software repository project. |
|
Obtain a project branch. |
|
Obtain a project tag. |
|
Create a project tag. |
|
Delete a project tag. |
|
Obtain the latest ten project commits. |
|
Obtain a project hook. |
|
Create a project hook. |
|
Delete a project hook. |
|
Obtain a repository file directory. |
|
Obtain repository file contents. |
|
Create a repository file. |
|
Modify repository file contents. |
|
Delete repository file contents. |
Dynamic Configuration
API |
Description |
---|---|
Import configurations to the configuration management center. |
|
Export configurations from the configuration management center. |
Engine Management
API |
Description |
---|---|
Querying Flavors Supported by an Exclusive Microservice Engine |
Query the flavors supported by an exclusive microservice engine. |
Query the exclusive microservice engine list. |
|
Create an exclusive microservice engine. |
|
Query details about an exclusive microservice engine. |
|
Delete an exclusive microservice engine. |
|
Query details about an exclusive microservice engine job. |
Authentication
API |
Description |
---|---|
Obtaining the User Token of an Exclusive Microservice Engine |
This API is intended only for exclusive microservice engines with security authentication enabled. Before accessing APIs of an exclusive microservice engine with security authentication enabled, you need to call this API to obtain a user token. This token is the unique credential for accessing the APIs. |
Microservice
API |
Description |
---|---|
Query the definition information about a microservice based on serviceId. |
|
Delete the definition and related information about a microservice, and deregisters all instances of the microservice. |
|
Query information about microservices that meet filter criteria. |
|
Create static information for a microservice before registering a microservice instance. The registered instance is associated with the static information based on the serviceId field. One service corresponds to multiple instances. The serviceId field can be customized. If serviceId is not customized, the system generates a random serviceId. |
|
Delete the definitions and related information about microservices in batches, and deregisters all instances of the microservices. |
|
Modify static information about a microservice To update some fields in the static information, input all static information (including the fields that do not need to be updated) in JSON format. |
|
Query the unique serviceId or schema ID of a microservice based on filter criteria. |
Schema
API |
Description |
---|---|
Query a microservice schema based on service_id and schema_id. |
|
Modify a microservice schema based on schema_id. |
|
Query all schema information (including schemaId and summary) about a microservice. |
Microservice Instance
API |
Description |
---|---|
Register a microservice instance after a microservice is created. Information about the instance must be provided during registration. instanceId can be customized. If it is customized, all contents are overwritten upon re-registration. If it is not customized, the system automatically generates an ID. If the endpoint content is duplicate, the original ID is used. |
|
Query all instances of a microservice based on service_id after the instances are registered. |
|
Deregister an instance based on instance_id after the instance is registered. |
|
Query details about an instance based on service_id and instance_id after the instance is registered. |
|
Modifying the Extended Information About a Microservice Instance |
Add or update the extended information about a microservice instance based on instance_id after the instance is registered. |
Modify the status of a microservice instance based on instance_id after the instance is registered. |
|
Send heartbeat information from service provider to service center, so that the service center can check whether service instances are normal. |
|
Query a microservice instance based on microservice version rules or field filter criteria after the instance is registered. |
|
Query microservice instances in batches based on microservice version rules or field filter criteria after the instances are registered. |
Dependency
API |
Description |
---|---|
Query all providers of a microservice based on consumer_id. For example, if service A depends on services B and C, you can query the information about services B and C based on service A ID. |
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot