Querying the pg_hba.conf Change History of a DB Instance
Function
This API is used to query the pg_hba.conf change history of a DB instance.
- Before calling this API, learn how to authenticate it.
- Before calling this API, learn about request header parameters.
- Parameter description
Table 1 Parameters Parameter
Mandatory
Description
project_id
Yes
Definition
Project ID of a tenant in a region.
To obtain the value, see Obtaining a Project ID.
Constraints
N/A
Range
N/A
Default Value
N/A
instance_id
Yes
Definition
Instance ID.
Constraints
N/A
Range
N/A
Default Value
N/A
Table 2 Request parameters Parameter
Mandatory
Type
Description
start_time
No
String
Definition
Start time.
Constraints
N/A
Range
N/A
Default Value
If this parameter is not specified, 00:00 (UTC time zone) on the current day is used by default.
end_time
No
String
Definition
End time.
Constraints
N/A
Range
N/A
Default Value
If this parameter is not specified, the current time (UTC time zone) is used by default.
Request
Response
- Normal response
Table 3 Parameters Parameter
Type
Description
Array elements
Array of objects
Definition
Parameter list.
For details, see Table 4.
Table 4 Parameters Parameter
Type
Description
status
String
Definition
Change result.
Range
- success: The change has taken effect.
- failed: The change did not take effect.
- setting: The change is in progress.
time
String
Definition
Time when the change was made.
Range
N/A
fail_reason
String
Definition
Reason for a change failure.
Range
N/A
before_confs
Array of objects
Definition
Original values.
For details, see Table 5.
after_confs
Array of objects
Definition
New values.
For details, see Table 6.
Table 5 before_confs field description Parameter
Type
Description
type
String
Definition
Connection type.
Range
Enumerated values: host, hostssl, and hostnossl
database
String
Definition
Database name.
Range
The value can be any name other than template0 and template1. Use commas (,) to separate multiple names.
user
String
Definition
Name of a user other than rdsAdmin, rdsMetric, rdsBackup, rdsRepl, and rdsProxy.
Range
- all indicates all database users of the DB instance.
- Use commas (,) to separate multiple usernames.
address
String
Definition
Client IP address. 0.0.0.0/0 indicates that the user can access the database from any IP address.
Range
N/A
mask
String
Definition
Subnet mask.
Range
The value is an empty character string by default.
method
String
Definition
Authentication mode.
Range
Enumerated values: reject, md5, and scram-sha-256
priority
Integer
Definition
Configuration priority.
Range
N/A
Table 6 after_confs field description Parameter
Type
Description
type
String
Definition
Connection type.
Range
Enumerated values: host, hostssl, and hostnossl
database
String
Definition
Database name.
Range
The value can be any name other than template0 and template1. Use commas (,) to separate multiple names.
user
String
Definition
Name of a user other than rdsAdmin, rdsMetric, rdsBackup, rdsRepl, and rdsProxy.
Range
- all indicates all database users of the DB instance.
- Use commas (,) to separate multiple usernames.
address
String
Definition
Client IP address. 0.0.0.0/0 indicates that the user can access the database from any IP address.
Range
N/A
mask
String
Definition
Subnet mask.
Range
The value is an empty character string by default.
method
String
Definition
Authentication mode.
Range
Enumerated values: reject, md5, and scram-sha-256
priority
Integer
Definition
Configuration priority.
Range
N/A
- Example normal response
[ { "status" : "success", "time" : "2023-08-01 09:00:00", "fail_reason" : "", "before_confs" : [ { "type" : "host", "database" : "all", "user" : "all", "address" : "0.0.0.0/0", "mask" : "", "method" : "md5", "priority" : 0 } ], "after_confs" : [ { "type" : "hostssl", "database" : "all", "user" : "all", "address" : "0.0.0.0/0", "mask" : "", "method" : "md5", "priority" : 0 } ] } ]
- Abnormal response
For details, see Abnormal Request Results.
Status Code
- Normal
- Abnormal
For details, see Status Codes.
Error Code
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