docs: fix dead service token deprecation link - #7752
docs: fix dead service token deprecation link#7752devin-ai-integration[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4518803f6f
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| <Accordion title="What is the difference between an identity and service token?"> | ||
| A service token is a project-level authentication method that is being deprecated in favor of identities. The service token method will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys). | ||
| A service token is a project-level authentication method that is being deprecated in favor of identities. The service token method will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/api-key-management). |
There was a problem hiding this comment.
When readers follow this link for the promised deprecation notice and removal timeline, /blog/api-key-management does not provide that timeline—the commit description explicitly identifies it only as the closest live post. The replacement therefore leaves the FAQ's central claim unsupported; either republish/link the actual timeline or revise the sentence so it accurately describes what the article contains.
AGENTS.md reference: AGENTS.md:L15-L17
Useful? React with 👍 / 👎.
|
| Filename | Overview |
|---|---|
| docs/documentation/platform/identities/machine-identities.mdx | Replaces a 404ing blog link with a live destination; no unacknowledged actionable issue remains in the changed line. |
Reviews (1): Last reviewed commit: "docs: point service token FAQ at the liv..." | Re-trigger Greptile
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
1 participant
Context
The service token FAQ on the machine identities page links to
https://infisical.com/blog/deprecating-api-keysfor the deprecation notice and timeline. That post was deleted with no redirect, so the link has been 404ing for roughly 18 months — it points readers at nothing exactly when they are looking for the removal timeline. It now points at/blog/api-key-management, the closest live post.Two caveats worth flagging: there is no longer a public page stating the deprecation timeline, so the surrounding sentence promises more than the destination delivers — someone should decide whether that timeline gets republished or the wording changes. The same dead URL is also hardcoded in two frontend components (
PersonalTabGroup.tsx,ServiceTokenTab.tsx); left alone here to keep this a docs-only change. Infisical/infisical-web#274 adds a redirect for the old URL, which covers those two in-app links in the meantime.Steps to verify the change
Open
/documentation/platform/identities/machine-identitiesand follow the link in the "What is the difference between an identity and service token?" FAQ entry; it resolves instead of 404ing.Type
Checklist
Link to Devin session: https://app.devin.ai/sessions/9000f41296d04f57a9f04f123a3f20f6