a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
109 lines
4.4 KiB
Markdown
109 lines
4.4 KiB
Markdown
---
|
||
layout: "api"
|
||
page_title: "PostgreSQL - Database - Secrets Engines - HTTP API"
|
||
sidebar_title: "PostgreSQL"
|
||
sidebar_current: "api-http-secret-databases-postgresql"
|
||
description: |-
|
||
The PostgreSQL plugin for Vault's database secrets engine generates database credentials to access PostgreSQL servers.
|
||
---
|
||
|
||
# PostgreSQL Database Plugin HTTP API
|
||
|
||
The PostgreSQL database plugin is one of the supported plugins for the database
|
||
secrets engine. This plugin generates database credentials dynamically based on
|
||
configured roles for the PostgreSQL database.
|
||
|
||
## Configure Connection
|
||
|
||
In addition to the parameters defined by the [Database
|
||
Backend](/api/secret/databases/index.html#configure-connection), this plugin
|
||
has a number of parameters to further configure a connection.
|
||
|
||
| Method | Path | Produces |
|
||
| :------- | :--------------------------- | :--------------------- |
|
||
| `POST` | `/database/config/:name` | `204 (empty body)` |
|
||
|
||
### Parameters
|
||
- `connection_url` `(string: <required>)` - Specifies the PostgreSQL DSN. This field
|
||
can be templated and supports passing the username and password
|
||
parameters in the following format {{field_name}}. A templated connection URL is
|
||
required when using root credential rotation.
|
||
|
||
- `max_open_connections` `(int: 2)` - Specifies the maximum number of open
|
||
connections to the database.
|
||
|
||
- `max_idle_connections` `(int: 0)` - Specifies the maximum number of idle
|
||
connections to the database. A zero uses the value of `max_open_connections`
|
||
and a negative value disables idle connections. If larger than
|
||
`max_open_connections` it will be reduced to be equal.
|
||
|
||
- `max_connection_lifetime` `(string: "0s")` - Specifies the maximum amount of
|
||
time a connection may be reused. If <= 0s connections are reused forever.
|
||
|
||
- `username` `(string: "")` - The root credential username used in the connection URL.
|
||
|
||
- `password` `(string: "")` - The root credential password used in the connection URL.
|
||
|
||
### Sample Payload
|
||
|
||
```json
|
||
{
|
||
"plugin_name": "postgresql-database-plugin",
|
||
"allowed_roles": "readonly",
|
||
"connection_url": "postgresql://{{username}}:{{password}}@localhost:5432/postgres",
|
||
"max_open_connections": 5,
|
||
"max_connection_lifetime": "5s",
|
||
"username": "username",
|
||
"password": "password"
|
||
}
|
||
```
|
||
|
||
### Sample Request
|
||
|
||
```
|
||
$ curl \
|
||
--header "X-Vault-Token: ..." \
|
||
--request POST \
|
||
--data @payload.json \
|
||
http://127.0.0.1:8200/v1/database/config/postgresql
|
||
```
|
||
|
||
## Statements
|
||
|
||
Statements are configured during role creation and are used by the plugin to
|
||
determine what is sent to the database on user creation, renewing, and
|
||
revocation. For more information on configuring roles see the [Role
|
||
API](/api/secret/databases/index.html#create-role) in the database secrets engine docs.
|
||
|
||
### Parameters
|
||
|
||
The following are the statements used by this plugin. If not mentioned in this
|
||
list the plugin does not support that statement type.
|
||
|
||
- `creation_statements` `(list: <required>)` – Specifies the database
|
||
statements executed to create and configure a user. Must be a
|
||
semicolon-separated string, a base64-encoded semicolon-separated string, a
|
||
serialized JSON string array, or a base64-encoded serialized JSON string
|
||
array. The '{{name}}', '{{password}}' and '{{expiration}}' values will be
|
||
substituted.
|
||
|
||
- `revocation_statements` `(list: [])` – Specifies the database statements to
|
||
be executed to revoke a user. Must be a semicolon-separated string, a
|
||
base64-encoded semicolon-separated string, a serialized JSON string array, or
|
||
a base64-encoded serialized JSON string array. The '{{name}}' value will be
|
||
substituted. If not provided defaults to a generic drop user statement.
|
||
|
||
- `rollback_statements` `(list: [])` – Specifies the database statements to be
|
||
executed rollback a create operation in the event of an error. Not every
|
||
plugin type will support this functionality. Must be a semicolon-separated
|
||
string, a base64-encoded semicolon-separated string, a serialized JSON string
|
||
array, or a base64-encoded serialized JSON string array. The '{{name}}' value
|
||
will be substituted.
|
||
|
||
- `renew_statements` `(list: [])` – Specifies the database statements to be
|
||
executed to renew a user. Not every plugin type will support this
|
||
functionality. Must be a semicolon-separated string, a base64-encoded
|
||
semicolon-separated string, a serialized JSON string array, or a
|
||
base64-encoded serialized JSON string array. The '{{name}}' and
|
||
'{{expiration}}` values will be substituted.
|