awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-07 11:27:32 +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
docs/integrations/app-connections/hashicorp-vault.mdx
+20 -11
View File
@@ -39,19 +39,28 @@ Infisical supports two methods for connecting to Hashicorp Vault.
<Step title="Create Policy"> <Step title="Create Policy">
You may name your policy whatever you want, but remember the name as it will be used in future steps. You may name your policy whatever you want, but remember the name as it will be used in future steps.
<Note> Depending on your use case, you may have different policy configurations:
Ensure that you replace the policy path so that it matches with an existing KV Secrets Engine mount and path.
</Note>
```hcl <Tabs>
path "demo_mount/data/demo_path/demo_subpath" { <Tab title="Secret Sync">
capabilities = [ "create", "read", "update" ] ```hcl
} path "demo_mount/data/demo_path/demo_subpath" {
capabilities = [ "create", "read", "update" ]
}
path "sys/mounts" { path "sys/mounts" {
capabilities = ["read"] 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) ![Vault Create Policy](/images/app-connections/hashicorp-vault/vault-create-policy.png)
</Step> </Step>