awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-02 19:25:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Review fixes

Browse Source
This commit is contained in:
x032205
2025-09-02 18:52:08 -04:00
parent f7828ed458
commit c29b5e37f3
12 changed files with 12 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/app-connections/hashicorp-vault.mdx
+2 -2
View File
@@ -149,7 +149,7 @@ Infisical supports two methods for connecting to Hashicorp Vault.
<Tab title="App Role">
- **Name**: The name of the connection being created. Must be slug-friendly.
- **Description**: An optional description to provide details about this connection.
- **Gateway (optional):** The gateway connected to your private network.
- **Gateway (optional):** The gateway connected to your private network. All requests made to your Vault instance will be made through the configured gateway.
- **Instance URL**: The URL of your Hashicorp Vault instance.
- **Namespace (optional)**: The namespace within your vault. Self-hosted and enterprise clusters may not use namespaces.
- **Role ID**: The Role ID generated in the steps above.
@@ -158,7 +158,7 @@ Infisical supports two methods for connecting to Hashicorp Vault.
<Tab title="Access Token">
- **Name**: The name of the connection being created. Must be slug-friendly.
- **Description**: An optional description to provide details about this connection.
- **Gateway (optional):** The gateway connected to your private network.
- **Gateway (optional):** The gateway connected to your private network. All requests made to your Vault instance will be made through the configured gateway.
- **Instance URL**: The URL of your Hashicorp Vault instance.
- **Namespace (optional)**: The namespace within your vault. Self-hosted and enterprise clusters may not use namespaces.
- **Access Token**: The Access Token generated in the steps above.