Fix broken external links found with automated link checking (#424)

* Initial plan

* Add check-links.yml workflow with all PR #424 feedback applied

Co-authored-by: TimHess <3947063+TimHess@users.noreply.github.com>

* Address all bart-vmware review feedback on check-links.yml and build-and-stage.yml

Co-authored-by: TimHess <3947063+TimHess@users.noreply.github.com>

* add link-checking of internal links of built site content

* process improvements, add local script for checking links from all docfx files

- ignore razor routes from static file checking
- alter root-dir to avoid errors with asset links

* focus on external link checking in static content

- drop changes to build-and-stage
- replace .ps1 with equivalent of check-links.yml

* drop branch filter from PR trigger

* fix lychee install link

* focus check-links job on external links, exclude vendored sources

Co-authored-by: Cursor <cursoragent@cursor.com>
Made-with: Cursor

* add --root-dir to resolve root-relative image paths without error

Made-with: Cursor

* Update .github/workflows/check-links.yml

Co-authored-by: Bart Koelman <104792814+bart-vmware@users.noreply.github.com>

* PR suggests and alphabetize lychee params

- only use --no-progress in CI
- use more defaults
- change settings per-host instead of globally
- check for installed lychee first

* re-add root-dir, primarily for running in CI

* re-add --verbose, local script enhancements

--verbose is needed to see redirect details
- locally:
  - set user-agent locally to avoid 403 on mysql links (doesn't seem to affect CI)
  - ignore build/docfx-net10-binaries (like playwright readme)
- longer host-request-interval and retry-wait-time

* move settings to shared lychee.toml

- since redirect fixes are already in place in other PR, change verbosity now

* fix exclude_paths broken in move to lychee.toml

* isolate lychee caching to specific workstreams

- also include a paste-able snippet to bust the cache for a given PR

* Fix broken links

- external links to
  - CredHub API, Spring AMQP, and Spring Cloud projects
  - Broadcom/Pivotal/samples/Microsoft
- CredHub/Samples/CircuitBreaker links
- Reduce external redirects
- Fix double 'the' in fileshares usage docs
- Disambiguate Redis/Valkey versions, clarify Thinktecture reference
- Fix 'n0t' typo in v3 fileshares docs
- TAS SSO→Single Sign-On

Co-authored-by: TimHess <3947063+TimHess@users.noreply.github.com>

* fix absolute .md links to relative paths

* fix consul-register-example casing, fix broken eureka docs link

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix anchors, reduce unnecessary redirects

- redirect reductions for docs.microsoft.com and trailing slashes
- remove /en-US/ from mozilla links

* use default verbosity, update cosmos connectionstring link

* drop training page

* Apply suggestions from code review

Co-authored-by: Bart Koelman <104792814+bart-vmware@users.noreply.github.com>

* address PR 424 review feedback

- CredHub "on Tanzu Platform" links updated to Broadcom TechDocs (v2, v3)
- Hystrix flow chart anchor corrected from #collapser-flow to #flow-chart (v2, v3)
- NuGet profile URL corrected to SteeltoeOSS
- CosmosDB, MySQL, PostgreSQL v2/v3: restore original broker names, drop dead
  links, add notes where service broker support has been retired
- Redis v4: deduplicate Valkey links, rename to "Tanzu for Valkey on Tanzu Platform"
- "Getting Started with C#" link updated to learn.microsoft.com/dotnet/csharp (v2, v3)

Made-with: Cursor

* Update docs/docs/v2/connectors/cosmosdb.md

Co-authored-by: Bart Koelman <104792814+bart-vmware@users.noreply.github.com>

* More PR feedback

- #-loggregator-firehose-architecture
- exclude mysql.com from lychee scan
- restore Consul-Register-Example casing, use case-insensitive exclusion
- fix consul add package example

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: TimHess <3947063+TimHess@users.noreply.github.com>
Co-authored-by: Tim Hess <tim.hess@broadcom.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Bart Koelman <104792814+bart-vmware@users.noreply.github.com>

Author: 4 people

AGENTS.md

@@ -40,5 +40,5 @@ This repository hosts the [Steeltoe website](https://steeltoe.io/): documentatio
 ## Resources
 
 - **Canonical instructions:** [README.md](README.md), [build/README.md](build/README.md), [docs/README.md](docs/README.md).
-- [docfx documentation](https://dotnet.github.io/docfx) · [docfx Flavored Markdown](https://dotnet.github.io/docfx/docs/markdown.html)
+- [docfx documentation](https://dotnet.github.io/docfx/) · [docfx Flavored Markdown](https://dotnet.github.io/docfx/docs/markdown.html)
 - [Steeltoe website](https://steeltoe.io) · [ASP.NET Core Blazor](https://learn.microsoft.com/aspnet/core/blazor/)

README.md

@@ -4,7 +4,7 @@
 
 This is the home of the [Steeltoe website](https://steeltoe.io/), which hosts documentation and blog articles.
 
-The website is built with [ASP.NET Core Blazor](https://learn.microsoft.com/aspnet/core/blazor/) and [docfx](https://dotnet.github.io/docfx).
+The website is built with [ASP.NET Core Blazor](https://learn.microsoft.com/aspnet/core/blazor/) and [docfx](https://dotnet.github.io/docfx/).
 docfx generates API documentation from triple-slash comments in Steeltoe source code and converts [Markdown](https://dotnet.github.io/docfx/docs/markdown.html) documents to HTML.
 
 ## Building and running the site

docs/README.md

@@ -1,6 +1,6 @@
 # Directory Contents
 
-The directories below this one are used with [docfx](https://dotnet.github.io/docfx) to generate static HTML files that are served from the `/src/Steeltoe.io/wwwroot` directory.
+The directories below this one are used with [docfx](https://dotnet.github.io/docfx/) to generate static HTML files that are served from the `/src/Steeltoe.io/wwwroot` directory.
 
 | Path | Description |
 | --- | --- |

docs/api/v2/index.md

@@ -23,7 +23,7 @@ Contains several packages that are common to other Steeltoe components.
 
 ## Steeltoe Configuration Providers
 
-[Custom configuration providers](https://docs.microsoft.com/aspnet/core/fundamentals/configuration/#custom-configuration-providers) for use with Microsoft's [application configuration](https://docs.microsoft.com/aspnet/core/fundamentals/configuration) for accessing configuration settings for an application.
+[Custom configuration providers](https://learn.microsoft.com/aspnet/core/fundamentals/configuration/#custom-configuration-provider) for use with Microsoft's [application configuration](https://learn.microsoft.com/aspnet/core/fundamentals/configuration) for accessing configuration settings for an application.
 
 [view](Steeltoe.Extensions.Configuration.yml)
 

docs/api/v3/index.md

@@ -29,7 +29,7 @@ Contains several packages that are common to other Steeltoe components.
 
 ## Steeltoe Configuration Providers
 
-[Custom configuration providers](https://docs.microsoft.com/aspnet/core/fundamentals/configuration/#custom-configuration-providers) for use with Microsoft's [application configuration](https://docs.microsoft.com/aspnet/core/fundamentals/configuration) for accessing configuration settings for an application.
+[Custom configuration providers](https://learn.microsoft.com/aspnet/core/fundamentals/configuration/#custom-configuration-provider) for use with Microsoft's [application configuration](https://learn.microsoft.com/aspnet/core/fundamentals/configuration) for accessing configuration settings for an application.
 
 [view](Steeltoe.Extensions.Configuration.yml)
 

docs/api/v4/index.md

@@ -23,7 +23,7 @@ Various general-purpose facilities, often used by higher-level Steeltoe componen
 
 ## Steeltoe.Configuration
 
-[Custom configuration providers](https://docs.microsoft.com/aspnet/core/fundamentals/configuration/#custom-configuration-providers) for use with Microsoft's [application configuration](https://docs.microsoft.com/aspnet/core/fundamentals/configuration/) for accessing configuration settings for an application.
+[Custom configuration providers](https://learn.microsoft.com/aspnet/core/fundamentals/configuration/#custom-configuration-provider) for use with Microsoft's [application configuration](https://learn.microsoft.com/aspnet/core/fundamentals/configuration/) for accessing configuration settings for an application.
 
 [view](Steeltoe.Configuration.yml)
 

docs/articles/create-dotnet-microservice-projects-automatically-with-steeltoe-initializr.md

@@ -89,7 +89,7 @@ Below is a brief explanation of Initializr's top level endpoints. But the conver
 
   **Service Configuration**
 
-  The config endpoint ([https://start.steeltoe.io/api/config/](https://start.steeltoe.io/api/config/)) provides a way to get how Initializr has been configured. This endpoint has quite a few sub-endpoints that let you drill deeper into specific config values. Say you wanted to know what .NET runtimes are supported as well what the default version is. You could send a request to [https://start.steeltoe.io/api/config/dotNetFrameworks](https://start.steeltoe.io/api/config/dotNetFrameworks) and receive a JSON formatted answer.
+  The config endpoint ([https://start.steeltoe.io/api/uiconfig/](https://start.steeltoe.io/api/uiconfig/)) provides a way to get how Initializr has been configured. This endpoint has quite a few sub-endpoints that let you drill deeper into specific config values. Say you wanted to know what .NET runtimes are supported as well what the default version is. You could send a request to [https://start.steeltoe.io/api/uiconfig/dotNetFrameworks](https://start.steeltoe.io/api/uiconfig/dotNetFrameworks) and receive a JSON formatted answer.
 
   You can create quite a rich set of tooling with the config endpoint. In true cloud-native design, you can run instances of Initializr in different environments while the tooling keeps a consistent experience.
 

docs/articles/index.md

@@ -58,7 +58,7 @@ uid: articles
         </a>
     </li>
     <li class="blog-item">
-        <a href="https://techcommunity.microsoft.com/t5/apps-on-azure/net-and-java-together-in-azure-spring-cloud-with-pet-clinic/ba-p/2087416">
+        <a href="https://techcommunity.microsoft.com/blog/appsonazureblog/-net-and-java-together-in-azure-spring-cloud-with-pet-clinic/2087416">
             <span class="blog-date" href="">January 25 2021</span>
             <div class="blog-author">David Dieruf</div><br>
             <div class="blog-title" style="display:inline-block">.NET and Java together in Azure Spring Cloud with Pet Clinic</div>

docs/articles/pivotal-contributes-steeltoe-to-the-net-foundation.md

@@ -13,7 +13,7 @@ author.name: Zach Brown
 
 # Pivotal Contributes Steeltoe to the .NET Foundation
 
-It’s official: the Steeltoe open source project is joining the [.NET Foundation](https://www.dotnetfoundation.org/). That’s the news from Microsoft’s Connect() conference in New York City today....
+It’s official: the Steeltoe open source project is joining the [.NET Foundation](https://dotnetfoundation.org/). That’s the news from Microsoft’s Connect() conference in New York City today....
 
-| [Read More](https://tanzu.vmware.com/content/blog/pivotal-contributes-steeltoe-to-the-net-foundation) |
+| [Read More](https://blogs.vmware.com/tanzu/pivotal-contributes-steeltoe-to-the-net-foundation/) |
 | :---: |

docs/articles/releases/steeltoe-2-1-boosts-your-net-microservices-with-actuator-endpoints-distributed-tracing-and-deeper-support-for-the-frameworks-that-matter.md

@@ -25,5 +25,5 @@ The new features in Steeltoe 2.1, all based on community feedback, largely fall
 
 Let’s take a deeper look at each category...
 
-| [Read More](https://tanzu.vmware.com/content/blog/steeltoe-2-1-boosts-your-net-microservices-with-actuator-endpoints-distributed-tracing-and-deeper-support-for-the-frameworks-that-matter) |
+| [Read More](https://blogs.vmware.com/tanzu/steeltoe-2-1-boosts-your-net-microservices-with-actuator-endpoints-distributed-tracing-and-deeper-support-for-the-frameworks-that-matter/) |
 | :---: |