You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This terraform resource manages a HCP Vault Dedicated secret manager in Vault Radar. See Create a Vault policy https://developer.hashicorp.com/hcp/docs/vault-radar/agent/correlate-vault#create-a-vault-policy for details on creating the auth policy required.
-> **Note:** This feature is currently in private beta.
11
+
12
+
This terraform resource manages a HCP Vault Dedicated secret manager in Vault Radar. See [Create a Vault policy](https://developer.hashicorp.com/hcp/docs/vault-radar/agent/correlate-vault#create-a-vault-policy) for details on creating the auth policy required.
13
+
14
+
~> **Note:** A Radar agent is required before adding a Radar secret manager resource.
15
+
16
+
~> **Note:** One of the following authentication methods is required to create a Radar secret manager resource:
17
+
- Kubernetes
18
+
- AppRole
19
+
- Token
20
+
21
+
~> **Note:** Auth methods need to be configured in the `admin` namespace of the HCP Vault Dedicated cluster.
22
+
23
+
~> **Note:** Environment variables that correspond to the authentication method being used must be available to the agent.
-`vault_url` (String) Specify the URL of the Vault instance without protocol. Example: 'acme-public-vault-abc.def.z1.hashicorp.cloud:8200'.
63
+
64
+
### Optional
65
+
66
+
-`access_read_write` (Boolean) Indicates if the auth method has read and write access to the secrets engine. Defaults to false. Set this to true if you want to copy secrets to this secret manager as part of remediation process. (see https://developer.hashicorp.com/hcp/docs/vault-radar/remediate-secrets/copy-secrets)
67
+
-`approle_push` (Attributes) Configuration for AppRole Push-based authentication. Only one authentication method may be configured. (see [below for nested schema](#nestedatt--approle_push))
68
+
-`kubernetes` (Attributes) Configuration for Kubernetes-based authentication. Only one authentication method may be configured. (see [below for nested schema](#nestedatt--kubernetes))
69
+
-`project_id` (String) The ID of the HCP project where Vault Radar is located. If not specified, the project specified in the HCP Provider config block will be used, if configured.
70
+
-`token` (Attributes) Configuration for token-based authentication. Only one authentication method may be configured. (see [below for nested schema](#nestedatt--token))
71
+
72
+
### Read-Only
73
+
74
+
-`id` (String) The ID of this resource.
75
+
76
+
<aid="nestedatt--approle_push"></a>
77
+
### Nested Schema for `approle_push`
78
+
79
+
Required:
80
+
81
+
-`mount_path` (String) Mount path of the AppRole auth method in Vault. Example 'approle'.
82
+
-`role_id_env_var` (String) Environment variable containing the AppRole role ID. Example: 'VAULT_APPROLE_ROLE_ID'.
0 commit comments