cd5a0b056a
This also changes the api to make both pg_config and pg_bouncer_config optional parameters instead of required parameters for PATCH requests. The code already assumed the parameters were optional. Update the route code to require both pg_config and pgbouncer_config be set for POST requests. This isn't strictly required as committee enforces it, but in general we treat committee as an extra layer of protection and not as the sole validator.
7 lines
226 B
Plaintext
7 lines
226 B
Plaintext
! Invalid number of arguments for pg add-config-entries subcommand (requires: 1.., given: 0)
|
|
|
|
Add configuration entries to a PostgreSQL database
|
|
|
|
Usage:
|
|
ubi pg (location/pg-name | pg-id) add-config-entries key=value [...]
|