Remove obsolete configuration section links across multiple integrations #22011
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tegrations; these sections have been replaced by tabbed examples in the docs and inline examples in the app.
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
3 tasks
michaelcretzman
approved these changes
Dec 1, 2025
temporal-github-worker-1
bot
added
docs/approved
and removed
docs/review-requested
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR removes outdated links to Docker, Kubernetes, and ECS configuration “sections” across several integrations. These links redirected users to the general Integrations landing page in the app view and no longer matched the current tabbed layout in the docs.
Motivation
See original issue. I found the same pattern in two other integrations and updated those as well.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged