-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hvs pg rotating secret #1130
hvs pg rotating secret #1130
Changes from 17 commits
2bea744
c692880
ef8ddd0
cec063a
27c61e1
8a4cc73
b5f964f
e2273be
d49752a
b40ad71
54dbb93
39e4488
8fd171b
af25c58
894dce6
ab888ce
7005798
50e69d4
352afa2
f103962
51d1f49
f99e22e
fff07ba
f94d5bc
d88e499
3986d37
5c9afe4
9f747a6
068b7b9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
```release-note:feature | ||
Add `hcp_vault_secrets_integration_postgres` resource. | ||
``` | ||
|
||
```release-note:feature | ||
add postgres provider to hcp_vault_secrets_rotating_secret resource | ||
``` |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
--- | ||
# generated by https://github.com/hashicorp/terraform-plugin-docs | ||
page_title: "hcp_vault_secrets_integration_postgres Resource - terraform-provider-hcp" | ||
subcategory: "" | ||
description: |- | ||
The Vault Secrets Twilio integration resource manages a Twilio integration. | ||
--- | ||
|
||
# hcp_vault_secrets_integration_postgres (Resource) | ||
|
||
The Vault Secrets Twilio integration resource manages a Twilio integration. | ||
|
||
## Example Usage | ||
|
||
```terraform | ||
resource "hcp_vault_secrets_integration_postgres" "example" { | ||
name = "my-postgres-1" | ||
capabilities = ["ROTATION"] | ||
static_credential_details = { | ||
connection_string = "postgres://user:password@localhost:5432/dbname" | ||
} | ||
} | ||
``` | ||
|
||
<!-- schema generated by tfplugindocs --> | ||
## Schema | ||
|
||
### Required | ||
|
||
- `capabilities` (Set of String) Capabilities enabled for the integration. See the Vault Secrets documentation for the list of supported capabilities per provider. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I didn't find the matching documentation |
||
- `name` (String) The Vault Secrets integration name. | ||
|
||
### Optional | ||
|
||
- `project_id` (String) HCP project ID that owns the HCP Vault Secrets integration. Inferred from the provider configuration if omitted. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. where this can be found? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. not sure what you mean (this is consistent with other docs for other providers) |
||
- `static_credential_details` (Attributes) Postgres connection string (DSN) to the target database. (see [below for nested schema](#nestedatt--static_credential_details)) | ||
|
||
### Read-Only | ||
|
||
- `organization_id` (String) HCP organization ID that owns the HCP Vault Secrets integration. | ||
- `resource_id` (String) Resource ID used to uniquely identify the integration instance on the HCP platform. | ||
- `resource_name` (String) Resource name used to uniquely identify the integration instance on the HCP platform. | ||
|
||
<a id="nestedatt--static_credential_details"></a> | ||
### Nested Schema for `static_credential_details` | ||
|
||
Required: | ||
|
||
- `connection_string` (String, Sensitive) Connection string (DSN) for the Postgres database. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. where this can be found? |
||
|
||
## Import | ||
|
||
Import is supported using the following syntax: | ||
|
||
```shell | ||
terraform import hcp_vault_secrets_integration_confluent.example my-postgres-1 | ||
dhuckins marked this conversation as resolved.
Show resolved
Hide resolved
|
||
``` |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
terraform import hcp_vault_secrets_integration_confluent.example my-postgres-1 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
resource "hcp_vault_secrets_integration_postgres" "example" { | ||
name = "my-postgres-1" | ||
capabilities = ["ROTATION"] | ||
static_credential_details = { | ||
connection_string = "postgres://user:password@localhost:5432/dbname" | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should it be named postgresql?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, postgres is correct