awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-09-22 13:39:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

nit: make docs a bit more future proof and descriptive

Browse Source
This commit is contained in:
x
2025-04-24 23:48:09 -04:00
parent fd0a00023b
commit a5b5b90ca1
1 changed files with 20 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
docs/integrations/app-connections/hashicorp-vault.mdx
View File

@@ -39,19 +39,28 @@ Infisical supports two methods for connecting to Hashicorp Vault.
<Step title="Create Policy">
You may name your policy whatever you want, but remember the name as it will be used in future steps.
<Note>
Ensure that you replace the policy path so that it matches with an existing KV Secrets Engine mount and path.
</Note>
Depending on your use case, you may have different policy configurations:
```hcl
path "demo_mount/data/demo_path/demo_subpath" {
capabilities = [ "create", "read", "update" ]
}
<Tabs>
<Tab title="Secret Sync">
```hcl
path "demo_mount/data/demo_path/demo_subpath" {
capabilities = [ "create", "read", "update" ]
}
path "sys/mounts" {
capabilities = ["read"]
}
```
path "sys/mounts" {
capabilities = ["read"]
}
```
- **demo_mount**: The name of the target secrets engine (e.g., 'secret', 'kv').
- **demo_path/demo_subpath**: The specific path within the secrets engine where secrets are stored.
<Note>
Ensure that you replace the policy path so that it matches with an existing KV Secrets Engine mount and path.
</Note>
</Tab>
</Tabs>
![Vault Create Policy](/images/app-connections/hashicorp-vault/vault-create-policy.png)
</Step>