Fix broken anchor link for #verbose-logging #17136
Open
+6
−0
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
Adds JavaScript redirect from old /docs/support/troubleshooting/#verbose-logging anchor to the new location at /docs/support/debugging/logging/#cli-verbose-logging. This fixes broken links in older provider versions that reference the old URL. Fixes pulumi#16985
Member
Author
|
Looks like this is failing because I pushed from a fork. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds a JavaScript redirect for the old
/docs/support/troubleshooting/#verbose-logginganchor to redirect to the new location at/docs/support/debugging/logging/#cli-verbose-logging.Details
Older versions of Pulumi Azure Native (and potentially other providers) contain hardcoded links to the
#verbose-logginganchor on the troubleshooting page. When the troubleshooting documentation was reorganized, the verbose logging content was moved to a dedicated logging page, breaking these links.This fix follows the same pattern as the existing
#conflictredirect already in place, ensuring users following old documentation links are automatically redirected to the correct location.Testing
#conflictredirectFixes #16985