Create a ConfigMap in a namespace.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| sae:CreateConfigMap | create |
|
| none |
Request syntax
POST /pop/v1/sam/configmap/configMap HTTP/1.1
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| Name | string | Yes | The name of the ConfigMap. The name can contain digits, letters, and underscores (_). The name must start with a letter. | name |
| NamespaceId | string | Yes | The ID of the namespace to which the ConfigMap instance belongs. | cn-hangzhou |
| Data | object | No | The ID of the namespace to which the ConfigMap instance belongs. | |
| Data | string | Yes | The ConfigMap data. | {"env.shell": "/bin/sh"} |
| Description | string | No | The key-value pairs of the ConfigMap in the JSON format. Format: {"Data":"{"k1":"v1", "k2":"v2"}"} k specifies a key and v specifies a value. For more information, see Manage a Kubernetes ConfigMap. | test-desc |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "91F93257-7A4A-4BD3-9A7E-2F6EAE6D****",
"Message": "success",
"TraceId": "0a98a02315955564772843261e****",
"Data": {
"ConfigMapId": 1
},
"ErrorCode": "The error code. Valid values:\n\n* If the call is successful, the **ErrorCode** parameter is not returned.\n* If the call fails, the **ErrorCode** parameter is returned. For more information, see the **Error codes** section in this topic.\n",
"Code": "200",
"Success": true
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | InvalidParameter.NotEmpty | You must specify the parameter %s. | - |
| 400 | InvalidParameter.Obviously | The specified parameter is invalid {%s}. | - |
| 400 | InvalidParameter.WithMessage | The parameter is invalid {%s}: %s | - |
| 400 | Exceed.ConfigMap | Too many ConfigMap objects have been created in the namespace. | - |
| 400 | TooMany.Configmap | The maximum number of keys or the maximum length of Configmap is exceeded. | - |
| 500 | OperationFailed.RPCError | Internal RPC request processing error. | Internal RPC request processing error. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2021-11-25 | The Error code has changed | View Change Details |