Add redirect for #verbose-logging anchor to new logging documentation

[Copilot]

Older Pulumi Azure Native provider versions contain hardcoded links to /docs/support/troubleshooting/#verbose-logging. This anchor no longer exists after the troubleshooting page was reorganized into a hub and verbose logging content moved to /docs/support/debugging/logging/.

Changes

• Added JavaScript redirect in content/docs/support/troubleshooting/_index.md to redirect #verbose-logging anchor to /docs/support/debugging/logging/#cli-verbose-logging
• Follows existing pattern established by the #conflict redirect in the same file

if (window.location.hash === "#verbose-logging") {
  window.location = "/docs/support/debugging/logging/#cli-verbose-logging"
}

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Broken anchor link in older provider versions: docs/support/troubleshooting/#verbose-logging</issue_title>
<issue_description>### Summary

Older versions of Pulumi azure native contain a hardcoded link to /docs/support/troubleshooting/#verbose-logging that no longer resolves correctly. The troubleshooting page was reorganized into a hub page, and the verbose logging content moved to /docs/support/debugging/logging/.

Solution

Added a JavaScript redirect (similar to the existing #conflict redirect) in the troubleshooting _index.md:

if (window.location.hash === "#verbose-logging") {
window.location = "/docs/support/debugging/logging/#cli-verbose-logging"
}This ensures users following the old link from older provider versions are redirected to the correct documentation.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Broken anchor link in older provider versions: docs/support/troubleshooting/#verbose-logging #16985

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[claude]

Documentation Review

This PR successfully adds a JavaScript redirect for the #verbose-logging anchor that was broken after the troubleshooting page reorganization. The implementation follows the established pattern and correctly redirects to the new location.

✅ Verified

• Target URL /docs/support/debugging/logging/#cli-verbose-logging exists and anchor is correct
• File ends with newline as required by style guide
• JavaScript syntax is correct
• Follows existing redirect pattern in the same file

📝 Suggestion

The existing redirect for #conflict includes a GitHub issue reference comment for documentation. Consider adding one for this redirect as well:

// Redirect to the new verbose logging page
// https://github.com/pulumi/docs/issues/16985
if (window.location.hash === "#verbose-logging") {
  window.location = "/docs/support/debugging/logging/#cli-verbose-logging"
}

This helps future maintainers understand the context and find related discussions.

---

Mention @claude if you'd like additional reviews or fixes.

[pulumi-bot]

Your site preview for commit 6acad46 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17047-6acad465.s3-website.us-west-2.amazonaws.com.

[CamSoper]

@claude Implement your suggestion, please

[claude]

Claude finished @CamSoper's task in 42s —— View job

---

Implementation Complete ✅

• Read current file content
• Add GitHub issue reference comment
• Commit and push changes

Added the GitHub issue reference comment (https://github.com/pulumi/docs/issues/16985) above the #verbose-logging redirect, following the same pattern as the existing #conflict redirect.

The change has been committed and pushed to the copilot/fix-broken-anchor-link branch.

---

|

[CamSoper]

Automated changes approved. JavaScript redirect follows the established pattern and correctly handles the moved anchor. The target anchor #cli-verbose-logging exists on the destination page. Merging now.

[pulumi-bot]

Your site preview for commit 72a84e4 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17047-72a84e4a.s3-website.us-west-2.amazonaws.com.