mirror of
https://github.com/awatertrevi/infisical.git
synced 2026-09-22 13:39:35 +00:00
Start comb docs, integrations, intro, organization
This commit is contained in:
Tuan Dang
@@ -12,9 +12,9 @@ Prerequisites:
|
||||
|
||||
Navigate to your IAM user permissions and add a permission policy to grant access to AWS Parameter Store.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
For enhanced security, here's a custom policy containing the minimum permissions required by Infisical to sync secrets to AWS Parameter Store for the IAM user that you can use:
|
||||
|
||||
@@ -45,13 +45,13 @@ For enhanced security, here's a custom policy containing the minimum permissions
|
||||
|
||||
Obtain a AWS access key ID and secret access key for your IAM user in IAM > Users > User > Security credentials > Access keys
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the AWS Parameter Store tile and input your AWS access key ID and secret access key from the previous step.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -64,7 +64,7 @@ Press on the AWS Parameter Store tile and input your AWS access key ID and secre
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which AWS Parameter Store region and indicate the path for your secrets. Then, press create integration to start syncing secrets to AWS Parameter Store.
|
||||
|
||||
|
||||
|
||||
|
||||
<Tip>
|
||||
Infisical requires you to add a path for your secrets to be stored in AWS
|
||||
|
||||
@@ -12,9 +12,9 @@ Prerequisites:
|
||||
|
||||
Navigate to your IAM user permissions and add a permission policy to grant access to AWS Secrets Manager.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
For better security, here's a custom policy containing the minimum permissions required by Infisical to sync secrets to AWS Secrets Manager for the IAM user that you can use:
|
||||
|
||||
@@ -44,13 +44,13 @@ For better security, here's a custom policy containing the minimum permissions r
|
||||
|
||||
Obtain a AWS access key ID and secret access key for your IAM user in IAM > Users > User > Security credentials > Access keys
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the AWS Secrets Manager tile and input your AWS access key ID and secret access key from the previous step.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -63,7 +63,7 @@ Press on the AWS Secrets Manager tile and input your AWS access key ID and secre
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which AWS Secrets Manager region and under which secret name. Then, press create integration to start syncing secrets to AWS Secrets Manager.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
Infisical currently syncs environment variables to AWS Secrets Manager as
|
||||
|
||||
@@ -15,12 +15,12 @@ Prerequisites:
|
||||
|
||||
Obtain a Checkly API Key in User Settings > API Keys.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Checkly tile and input your Checkly API Key to grant Infisical access to your Checkly account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -33,8 +33,8 @@ Press on the Checkly tile and input your Checkly API Key to grant Infisical acce
|
||||
|
||||
Select which Infisical environment secrets you want to sync to Checkly and press create integration to start syncing secrets.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
In the new version of the Checkly integration, you are able to specify suffixes that depend on the secrets' environment and path.
|
||||
|
||||
@@ -14,22 +14,22 @@ Prerequisites:
|
||||
## Enter your Cloud 66 Access Token
|
||||
|
||||
In Cloud 66 Dashboard, click on the top right icon > Account Settings > Access Token
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Create new Personal Access Token.
|
||||
|
||||
|
||||
|
||||
Name it **infisical** and check **Public** and **Admin**. Then click "Create Token"
|
||||
|
||||
|
||||
|
||||
Copy and save your token.
|
||||
|
||||
|
||||
|
||||
### Go to Infisical Integration Page
|
||||
|
||||
Click on the Cloud 66 tile and enter your API token to grant Infisical access to your Cloud 66 account.
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -39,17 +39,17 @@ Click on the Cloud 66 tile and enter your API token to grant Infisical access to
|
||||
</Info>
|
||||
|
||||
Enter your Cloud 66 Personal Access Token here. Then click "Connect to Cloud 66".
|
||||
|
||||
|
||||
|
||||
|
||||
## Start integration
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Cloud 66 stacks and press create integration to start syncing secrets to Cloud 66.
|
||||
|
||||
|
||||
|
||||
<Warning>
|
||||
Any existing environment variables in Cloud 66 will be deleted when you start syncing. Make sure to add all the secrets into the Infisical dashboard first before doing any integrations.
|
||||
</Warning>
|
||||
|
||||
Done!
|
||||
|
||||
|
||||
|
||||
@@ -17,17 +17,17 @@ Obtain a Cloudflare [API token](https://dash.cloudflare.com/profile/api-tokens)
|
||||
|
||||
1. Create a new [API token](https://dash.cloudflare.com/profile/api-tokens) in My Profile > API Tokens
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
2. Copy your [Account ID](https://developers.cloudflare.com/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/) from Account > Workers & Pages > Overview
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Cloudflare Pages tile and input your Cloudflare API token and account ID to grant Infisical access to your Cloudflare Pages.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -40,5 +40,5 @@ Press on the Cloudflare Pages tile and input your Cloudflare API token and accou
|
||||
|
||||
Select which Infisical environment secrets you want to sync to Cloudflare and press create integration to start syncing secrets.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -10,10 +10,10 @@ Prerequisites:
|
||||
## Get your Digital Ocean Personal Access Tokens
|
||||
|
||||
On Digital Ocean dashboard, navigate to **API > Tokens** and click on "Generate New Token"
|
||||
|
||||
|
||||
|
||||
Name it **infisical**, choose **No expiry**, and make sure to check **Write (optional)**. Then click on "Generate Token" and copy your API token.
|
||||
|
||||
|
||||
|
||||
## Navigate to your project's integrations tab
|
||||
|
||||
@@ -28,12 +28,12 @@ Click on the **Digital Ocean App Platform** tile and enter your API token to gra
|
||||
</Info>
|
||||
|
||||
Then enter your Digital Ocean Personal Access Token here. Then click "Connect to Digital Ocean App Platform".
|
||||
|
||||
|
||||
|
||||
## Start integration
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Digital Ocean App and click "Create Integration".
|
||||
|
||||
|
||||
|
||||
Done!
|
||||
|
||||
|
||||
|
||||
@@ -15,12 +15,12 @@ Prerequisites:
|
||||
|
||||
Obtain a Fly.io access token in Access Tokens
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Fly.io tile and input your Fly.io access token to grant Infisical access to your Fly.io account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -33,5 +33,5 @@ Press on the Fly.io tile and input your Fly.io access token to grant Infisical a
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Fly.io app and press create integration to start syncing secrets to Fly.io.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -34,17 +34,17 @@ To begin, navigate to the cluster / namespace that you want to sync secrets to i
|
||||
|
||||
In Secrets, enable a KV Secrets Engine at a path for Infisical to sync secrets to; we'll use the path `kv`.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Enable the AppRole auth method
|
||||
|
||||
In Access > Auth Methods, enable the AppRole auth method.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Create an ACL Policy
|
||||
|
||||
@@ -67,9 +67,9 @@ path "sys/namespaces/*" {
|
||||
that we want to sync secrets to.
|
||||
</Note>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Create a role with the policy attached
|
||||
|
||||
@@ -77,7 +77,7 @@ We now create a `infisical` role with the generated token's time-to-live (TTL) s
|
||||
|
||||
1. Click the Vault CLI shell icon (`>_`) to open a command shell in the browser.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Copy the command below.
|
||||
|
||||
@@ -129,7 +129,7 @@ Great. We're now ready to connect Infisical to Vault!
|
||||
|
||||
Back in Infisical, press on the HashiCorp Vault tile and input your Vault instance and `infisical` role RoleID and SecretID.
|
||||
|
||||
|
||||
|
||||
|
||||
For additional details on each field:
|
||||
|
||||
@@ -137,7 +137,7 @@ For additional details on each field:
|
||||
|
||||
If using HCP, you can copy your Cluster URL in the Cluster Overview:
|
||||
|
||||
|
||||
|
||||
|
||||
- Vault Namespace: The Vault namespace you wish to connect to.
|
||||
- Vault RoleID: The RoleID previously created for the `infisical` role.
|
||||
@@ -154,8 +154,8 @@ For additional details on each field:
|
||||
|
||||
Press create integration to start syncing secrets to Vault.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -15,17 +15,17 @@ Prerequisites:
|
||||
|
||||
Obtain a Laravel Forge access token in API Tokens
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Obtain your Laravel Forge Server ID in Servers > Server ID
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Laravel Forge tile and input your Laravel Forge access token and server ID to grant Infisical access to your Laravel Forge account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -38,5 +38,5 @@ Press on the Laravel Forge tile and input your Laravel Forge access token and se
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Laravel Forge site and press create integration to start syncing secrets to Laravel Forge.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -16,12 +16,12 @@ Prerequisites:
|
||||
|
||||
Obtain a Northflank API token in Account settings > API > Tokens
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Northflank tile and input your Northflank API token to grant Infisical access to your Northflank account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -34,5 +34,5 @@ Press on the Northflank tile and input your Northflank API token to grant Infisi
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Northflank project and secret group. Finally, press create integration to start syncing secrets to Northflank.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -16,8 +16,8 @@ Prerequisites:
|
||||
|
||||
Obtain a Railway API Token in your Railway [Account Settings > Tokens](https://railway.app/account/tokens).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<Note>
|
||||
If this is your first time creating a Railway API token, then you'll be prompted to join
|
||||
@@ -29,7 +29,7 @@ Obtain a Railway API Token in your Railway [Account Settings > Tokens](https://r
|
||||
|
||||
Press on the Railway tile and input your Railway API Key to grant Infisical access to your Railway account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -42,7 +42,7 @@ Press on the Railway tile and input your Railway API Key to grant Infisical acce
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Railway project and environment (and optionally service). Lastly, press create integration to start syncing secrets to Railway.
|
||||
|
||||
|
||||
|
||||
|
||||
<Note>
|
||||
Infisical integrates with both Railway's [shared variables](https://blog.railway.app/p/shared-variables-release) at the project environment level as well as service variables at the service level.
|
||||
@@ -50,5 +50,5 @@ Select which Infisical environment secrets you want to sync to which Railway pro
|
||||
To sync secrets to a specific service in a project, you can select a service from the Railway Service dropdown; otherwise, leaving it empty will sync secrets to the shared variables of that project.
|
||||
</Note>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -15,12 +15,12 @@ Prerequisites:
|
||||
|
||||
Obtain a Render API Key in your Render Account Settings > API Keys.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Render tile and input your Render API Key to grant Infisical access to your Render account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -33,5 +33,5 @@ Press on the Render tile and input your Render API Key to grant Infisical access
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Render service and press create integration to start syncing secrets to Render.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -21,12 +21,12 @@ Prerequisites:
|
||||
## Enter your Supabase Access Token
|
||||
|
||||
Obtain a Supabase Access Token in your Supabase [Account > Access Tokens](https://app.supabase.com/account/tokens).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Supabase tile and input your Supabase Access Token to grant Infisical access to your Supabase account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -39,6 +39,6 @@ Press on the Supabase tile and input your Supabase Access Token to grant Infisic
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Supabase project. Lastly, press create integration to start syncing secrets to Supabase.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -15,17 +15,17 @@ Prerequisites:
|
||||
|
||||
Obtain a Terraform Cloud API Token in User Settings > Tokens
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Obtain your Terraform Cloud Workspace Id in Projects & Workspaces > Workspace > ID
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Terraform Cloud tile and input your Terraform Cloud API Token and Workspace Id to grant Infisical access to your Terraform Cloud account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -38,5 +38,5 @@ Press on the Terraform Cloud tile and input your Terraform Cloud API Token and W
|
||||
|
||||
Select which Infisical environment secrets and Terraform Cloud variable type you want to sync to which Terraform Cloud workspace/project and press create integration to start syncing secrets to Terraform Cloud.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -15,12 +15,12 @@ Prerequisites:
|
||||
|
||||
Obtain a [Windmill](https://www.windmill.dev/) access token in Access Tokens
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Press on the Windmill tile and input your Windmill access token to grant Infisical access to your Windmill account.
|
||||
|
||||
|
||||
|
||||
|
||||
<Info>
|
||||
If this is your project's first cloud integration, then you'll have to grant
|
||||
@@ -33,8 +33,8 @@ Press on the Windmill tile and input your Windmill access token to grant Infisic
|
||||
|
||||
Select which Infisical environment secrets you want to sync to which Windmill workspace and press create integration to start syncing secrets to Windmill.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<Warning>
|
||||
Secrets synced to Windmill are subject to the [ownership path
|
||||
|
||||
Reference in New Issue
Block a user