From 23b84d45a5e727a920ec71044091c7a759c9d64f Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Thu, 6 Feb 2025 20:01:22 +0000 Subject: [PATCH 1/2] Fix issue: WorkspaceTaskSubType.META_DESCRIPTION --- src/content/partials/fundamentals/create-token.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/partials/fundamentals/create-token.mdx b/src/content/partials/fundamentals/create-token.mdx index bf212c44b81fdb..39cb1d3d61e827 100644 --- a/src/content/partials/fundamentals/create-token.mdx +++ b/src/content/partials/fundamentals/create-token.mdx @@ -1,5 +1,7 @@ --- -{} +{ + description: "Create and manage API tokens in Cloudflare. Learn to set permissions, choose templates, and secure your tokens for effective API access." +} --- @@ -7,10 +9,8 @@ import { Render } from "~/components" :::note[Prerequisite] - Before you begin, [find your zone and account IDs](/fundamentals/setup/find-account-and-zone-ids/). - ::: 1. Determine if you want a user token or an [Account owned token](/fundamentals/api/get-started/account-owned-tokens/). Use Account owned tokens if you prefer service tokens that are not associated with users and your [desired API endpoints are compatible](/fundamentals/api/get-started/account-owned-tokens/#compatibility-matrix). From 35189a5cbb22e37f49b8329a1bbe5ad0d3aec61a Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Thu, 6 Feb 2025 20:01:25 +0000 Subject: [PATCH 2/2] Fix issue: WorkspaceTaskSubType.META_DESCRIPTION --- src/content/partials/fundamentals/account-owned-tokens.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/partials/fundamentals/account-owned-tokens.mdx b/src/content/partials/fundamentals/account-owned-tokens.mdx index 6259c83ed6eafa..0d46a6f34b6fcb 100644 --- a/src/content/partials/fundamentals/account-owned-tokens.mdx +++ b/src/content/partials/fundamentals/account-owned-tokens.mdx @@ -1,4 +1,4 @@ -While user tokens act on behalf of a particular user and inherit a subset of that user's permissions, account owned tokens allow you to set up durable integrations that can act as service principals with their own specific set of permissions. This approach is ideal for scenarios like CI/CD, or building integrations with external services like SEIMs where it is important that the integration continues working, even long after the user who configured the integration may have left your organization altogether. User tokens are better for ad hoc tasks like scripting, where acting as the user is ideal and durability is less of a concern. +description: Explore account owned tokens in Cloudflare's API, ideal for CI/CD and integrations, with specific permissions and durability beyond user tokens. ## Create an account owned token