Querying High-Risk Commands
Function
This API is used to query high-risk commands supported by a GeminiDB Redis instance.
Constraints
This API supports only proxy-based general-purpose GeminiDB Redis instances.
URI
GET /v3/{project_id}/instances/{instance_id}/high-risk-commands
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Explanation: Project ID of a tenant in a region. To obtain this value, see Obtaining a Project ID. Constraints: N/A Values: N/A Default value: N/A |
|
instance_id |
Yes |
String |
Explanation: Instance ID Constraints: N/A Values: N/A Default value: N/A |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
X-Auth-Token |
Yes |
String |
Explanation: User token Constraints: N/A Values: N/A Default value: N/A |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
commands |
Array of objects |
Explanation: High-risk commands and their corresponding renamed commands. For details, see Table 4. Values: N/A |
|
Parameter |
Type |
Description |
|---|---|---|
|
origin_name |
String |
Explanation: Original high-risk commands Values: keys, flushdb, flushall, hgetall, hkeys, hvals, and smembers |
|
name |
String |
Explanation: Name of an enabled command. If this parameter is left blank, the command is disabled. The value can contain a maximum of 30 characters, including digits, letters, and underscores (_). Values: N/A |
Example Request
GET https://{Endpoint}/v3/054e292c9880d4992f02c0196d3ea468/instances/41409e5a49ee467287d738b9b6d0adcbin12/high-risk-commands
Example Response
Status code: 200
Success
{
"commands" : [ {
"origin_name" : "keys",
"name" : "newKeys"
}, {
"origin_name" : "flushdb",
"name" : "newFlushdb"
}, {
"origin_name" : "flushall",
"name" : "newFlushall"
}, {
"origin_name" : "hgetall",
"name" : "newHgetall"
}, {
"origin_name" : "hkeys",
"name" : "newHkeys"
}, {
"origin_name" : "hvals",
"name" : "newHvals"
}, {
"origin_name" : "smembers",
"name" : "newSmembers"
} ]
}
Status Codes
For details, see Status Codes.
Error Codes
For details, see Error Codes.
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