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

Merge branch 'main' into feat/addHumanitecIntegration

Browse Source
This commit is contained in:
carlosmonastyrski
2025-03-13 10:55:40 -03:00
parent 39b323dd9c d9d62384e7
commit 1d14cdf334
103 changed files with 3196 additions and 567 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/integrations/cloud/databricks.mdx
View File

@@ -7,6 +7,12 @@ Prerequisites:
- Set up and add secrets to [Infisical Cloud](https://app.infisical.com)
<Note>
When integrating with Databricks, Infisical is intended to be the source of truth for the secrets in the configured Databricks scope.
Any secrets not present in Infisical will be removed from the specified scope. To prevent removal of secrets not managed by Infisical, Infisical recommends creating a designated secret scope for your integration.
</Note>
<Steps>
<Step title="Authorize Infisical for Databricks">
Obtain a Personal Access Token in **User Settings** > **Developer** > **Access Tokens**.

2
docs/integrations/secret-syncs/databricks.mdx
View File

@@ -34,6 +34,8 @@ description: "Learn how to configure a Databricks Sync for Infisical."
<Note>
You must create a secret scope in your Databricks workspace prior to configuration. Ensure your service principal has [Write permissions](https://docs.databricks.com/en/security/auth/access-control/index.html#secret-acls) for the specified secret scope.
Infisical recommends creating a designated Databricks secret scope for your sync to prevent removal of secrets not managed by Infisical.
</Note>
5. Configure the **Sync Options** to specify how secrets should be synced, then click **Next**.