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

Remove service token notice

Browse Source
This commit is contained in:
Maidul Islam
2024-09-16 21:25:53 -04:00
parent 3afcb19727
commit b886e66ee9
11 changed files with 2 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/integrations/cicd/jenkins.mdx
View File

@@ -138,16 +138,9 @@ Prerequisites:
</Tab>
<Tab title="Using CLI with Service Tokens (Deprecated)">
<Tab title="Using CLI with Service Tokens">
## Add Infisical Service Token to Jenkins
<Warning>
Service tokens are being deprecated in favor of [machine identities](/documentation/platform/identities/machine-identities).
They will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys).
**Please use our Jenkins Plugin instead!**
</Warning>
After setting up your project in Infisical and installing the Infisical CLI to the environment where your Jenkins builds will run, you will need to add the Infisical Service Token to Jenkins.
To generate a Infisical service token, follow the guide [here](/documentation/platform/token).

6
docs/integrations/cloud/aws-amplify.mdx
View File

@@ -62,12 +62,6 @@ This approach enables you to fetch secrets from Infisical during Amplify build t
</Tab>
<Tab title="Service Token (Deprecated)">
<Warning>
Service tokens are being deprecated in favor of [machine identities](/documentation/platform/identities/machine-identities).
They will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys).
</Warning>
<Steps>
<Step title="Generate a service token">

9
docs/integrations/platforms/docker-compose.mdx
View File

@@ -63,14 +63,7 @@ Follow this [guide](./docker) to configure the Infisical CLI for each service th
```
</Tab>
<Tab title="Service Token (Deprecated)">
<Warning>
Service tokens are being deprecated in favor of [machine identities](/documentation/platform/identities/machine-identities).
They will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys).
</Warning>
<Tab title="Service Token">
## Generate service token
Generate a unique [Service Token](/documentation/platform/token) for each service.

6
docs/integrations/platforms/docker.mdx
View File

@@ -83,12 +83,6 @@ CMD ["infisical", "run", "--projectId", "<your-project-id>", "--command", "npm r
</Tab>
<Tab title="Service Token (Deprecated)">
<Warning>
Service tokens are being deprecated in favor of [machine identities](/documentation/platform/identities/machine-identities).
They will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys).
</Warning>
```dockerfile
CMD ["infisical", "run", "--", "[your service start command]"]

6
docs/integrations/platforms/kubernetes.mdx
View File

@@ -587,12 +587,6 @@ spec:
</Accordion>
<Accordion title="authentication.serviceToken">
<Warning>
Service tokens are being deprecated in favor of [machine identities](/documentation/platform/identities/machine-identities).
They will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys).
</Warning>
The service token required to authenticate with Infisical needs to be stored in a Kubernetes secret. This block defines the reference to the name and namespace of secret that stores this service token.
Follow the instructions below to create and store the service token in a Kubernetes secrets and reference it in your CRD.