diff --git a/docs/cli/commands/export.mdx b/docs/cli/commands/export.mdx index 16c226084..6711903ec 100644 --- a/docs/cli/commands/export.mdx +++ b/docs/cli/commands/export.mdx @@ -51,7 +51,6 @@ infisical export --template= Alternatively, you may use service tokens. - Please note, however, that 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). ```bash # Example export INFISICAL_TOKEN= diff --git a/docs/cli/commands/run.mdx b/docs/cli/commands/run.mdx index bfa4bd693..c7872efb0 100644 --- a/docs/cli/commands/run.mdx +++ b/docs/cli/commands/run.mdx @@ -54,8 +54,6 @@ $ infisical run -- npm run dev Alternatively, you may use service tokens. - Please note, however, that 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). - ```bash # Example export INFISICAL_TOKEN= diff --git a/docs/cli/commands/secrets.mdx b/docs/cli/commands/secrets.mdx index 03ebde1c0..2dff5cf7b 100644 --- a/docs/cli/commands/secrets.mdx +++ b/docs/cli/commands/secrets.mdx @@ -33,7 +33,6 @@ $ infisical secrets Alternatively, you may use service tokens. - Please note, however, that 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). ```bash # Example export INFISICAL_TOKEN= diff --git a/docs/cli/usage.mdx b/docs/cli/usage.mdx index e372bd8cf..3569fd87e 100644 --- a/docs/cli/usage.mdx +++ b/docs/cli/usage.mdx @@ -206,8 +206,6 @@ infisical --domain="https://your-self-hosted-infisical.com/api" - Yes. Please note, however, that 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). - To use Infisical for non local development scenarios, please create a service token. The service token will allow you to authenticate and interact with Infisical. Once you have created a service token with the required permissions, you’ll need to feed the token to the CLI. ```bash diff --git a/docs/documentation/platform/token.mdx b/docs/documentation/platform/token.mdx index 13bd4cd19..af31f5a4a 100644 --- a/docs/documentation/platform/token.mdx +++ b/docs/documentation/platform/token.mdx @@ -3,13 +3,6 @@ title: "Service Token" description: "Infisical service tokens allow users to programmatically interact with Infisical." --- - - 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). - - - Service tokens are authentication credentials that services can use to access designated endpoints in the Infisical API to manage project resources like secrets. Each service token can be provisioned scoped access to select environment(s) and path(s) within them. diff --git a/docs/integrations/cicd/jenkins.mdx b/docs/integrations/cicd/jenkins.mdx index a83d90700..518237fc3 100644 --- a/docs/integrations/cicd/jenkins.mdx +++ b/docs/integrations/cicd/jenkins.mdx @@ -138,16 +138,9 @@ Prerequisites: - + ## Add Infisical Service Token to Jenkins - - 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!** - - 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). diff --git a/docs/integrations/cloud/aws-amplify.mdx b/docs/integrations/cloud/aws-amplify.mdx index 761971025..6d3123b10 100644 --- a/docs/integrations/cloud/aws-amplify.mdx +++ b/docs/integrations/cloud/aws-amplify.mdx @@ -62,12 +62,6 @@ This approach enables you to fetch secrets from Infisical during Amplify build t - - - 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). - diff --git a/docs/integrations/platforms/docker-compose.mdx b/docs/integrations/platforms/docker-compose.mdx index 47715eb94..fea6b79a1 100644 --- a/docs/integrations/platforms/docker-compose.mdx +++ b/docs/integrations/platforms/docker-compose.mdx @@ -63,14 +63,7 @@ Follow this [guide](./docker) to configure the Infisical CLI for each service th ``` - - - - 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). - - + ## Generate service token Generate a unique [Service Token](/documentation/platform/token) for each service. diff --git a/docs/integrations/platforms/docker.mdx b/docs/integrations/platforms/docker.mdx index e858ddad0..6c059f8dd 100644 --- a/docs/integrations/platforms/docker.mdx +++ b/docs/integrations/platforms/docker.mdx @@ -83,12 +83,6 @@ CMD ["infisical", "run", "--projectId", "", "--command", "npm r - -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). - - ```dockerfile CMD ["infisical", "run", "--", "[your service start command]"] diff --git a/docs/integrations/platforms/kubernetes.mdx b/docs/integrations/platforms/kubernetes.mdx index 57329d4fd..bf72122b8 100644 --- a/docs/integrations/platforms/kubernetes.mdx +++ b/docs/integrations/platforms/kubernetes.mdx @@ -587,12 +587,6 @@ spec: - - 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). - - 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. diff --git a/docs/internals/service-tokens.mdx b/docs/internals/service-tokens.mdx index 39569326a..c48afd623 100644 --- a/docs/internals/service-tokens.mdx +++ b/docs/internals/service-tokens.mdx @@ -2,13 +2,6 @@ title: "Service tokens" description: "Understanding service tokens and their best practices." --- - - - 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). - - ​ Many clients use service tokens to authenticate and read/write secrets from/to Infisical; they can be created in your project settings.