This release is a pre-release and may not be stable for production use.
postgresql Resource Provider
The postgresql resource provider for Pulumi lets you manage postgresql resources in your cloud programs. To use this package, please install the Pulumi CLI first.
Installing
This package is available in many languages in the standard packaging formats.
Node.js (Java/TypeScript)
To use from JavaScript or TypeScript in Node.js, install using either npm:
$ npm install @pulumi/postgresql
or yarn:
$ yarn add @pulumi/postgresql
Python
To use from Python, install using pip:
$ pip install pulumi_postgresql
Go
To use from Go, use go get to grab the latest version of the library
$ go get github.com/pulumi/pulumi-postgresql/sdk/v3
.NET
To use from .NET, install using dotnet add package:
$ dotnet add package Pulumi.Postgresql
Configuration
The following configuration points are available:
postgresql:host- (required) The address for the postgresql server connection. Can also be specified with thePGHOSTenvironment variable.postgresql:port- (optional) The port for the postgresql server connection. The default is5432. Can also be specified with thePGPORTenvironment variable.postgresql:database- (optional) Database to connect to. The default ispostgres. Can also be specified with thePGDATABASEenvironment variable.postgresql:username- (required) Username for the server connection. The default ispostgres. Can also be specified with thePGUSERenvironment variable.postgresql:password- (optional) Password for the server connection. Can also be specified with thePGPASSWORDenvironment variable.postgresql:database_username- (optional) Username of the user in the database if different than connection username (See user name maps).postgresql:superuser- (optional) Should be set to false if the user to connect is not a PostgreSQL superuser (as is the case in RDS). In this case, some features might be disabled (e.g.: Refreshing state password from database).postgresql:sslmode- (optional) Set the priority for an SSL connection to the server. Valid values for sslmode are (note: prefer is not supported by Go's lib/pq):disable- No sslrequire- always SSL (the default, also skip verification)verify-ca- always SSL (verify that the certificate presented by the server was signed by a trusted CA)verify-full- Always SSL (verify that the certification presented by the server was signed by a trusted CA and the server host name matches the one in the certificate) Additional information on the options and their implications can be seen in the libpq(3) SSL guide. Can also be specified with thePGSSLMODEenvironment variable.
postgresql:connect_timeout- (optional) Maximum wait for connection, in seconds. The default is180s. Zero or not specified means wait indefinitely. Can also be specified with thePGCONNECT_TIMEOUTenvironment variable.postgresql:max_connections- (optional) Set the maximum number of open connections to the database. The default is4. Zero means unlimited open connections.postgresql:expected_version- (optional) Specify a hint to Terraform regarding the expected version that the provider will be talking with. This is a required hint in order for the provider to talk with an ancient version of PostgreSQL. This parameter is expected to be a PostgreSQL Version or current. Once a connection has been established, the provider will fingerprint the actual version. Default: 9.0.0.postgresql:clientcert- (optional) Clientcert block for configuring SSL certificate.postgresql:clientcert.cert- (required) The SSL client certificate file path. The file must contain PEM encoded data.postgresql:clientcert.key- (required) The SSL client certificate private key file path. The file must contain PEM encoded data.
Reference
For further information, please visit the postgresql provider docs or for detailed reference documentation, please visit the API docs.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-postgresql 3.11.0a1702406893
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pulumi_postgresql-3.11.0a1702406893.tar.gz | 42.2 kB | Without provenance | Details for pulumi_postgresql-3.11.0a1702406893.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pulumi_postgresql-3.11.0a1702406893-py3-none-any.whl | Python 3 | none | any | Details for pulumi_postgresql-3.11.0a1702406893-py3-none-any.whl |
Total release size: 108.4 kB
Release files / pulumi_postgresql-3.11.0a1702406893.tar.gz
| Download URL | pulumi_postgresql-3.11.0a1702406893.tar.gz |
|---|---|
| Size | 42.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d405474be3c6514df7662fc37446193b51c07c5af742ffe9565cf9c1bead018
|
|
BLAKE2b-256 checksum How to use checksums |
9fcd744a140850e8fbe39f0a0774e589ba6902e44030ff8f1d7115faeae8588d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / pulumi_postgresql-3.11.0a1702406893-py3-none-any.whl
| Download URL | pulumi_postgresql-3.11.0a1702406893-py3-none-any.whl |
|---|---|
| Size | 66.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f55e9a2f72fdef4fb4df19b522e3f00dcc3094c6f56aec87bdd40c9d3329659
|
|
BLAKE2b-256 checksum How to use checksums |
c410e7d6df302160456f1115eb3b01661619897b2f225b81be914271a6ff57fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for pulumi-postgresql 3.11.0a1702406893
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
