Add exclusion pattern for hub.docker.com to both production
and default link-checker configurations.
Docker Hub often implements rate limiting and bot detection that
causes false positive link validation failures in CI environments.
Moved to new tooling repo.
Removed package scripts for now.
Script Gets commands from source code and grep docs for commands- replaces the CLI audit script- searches tagged repo branch source code for CLI commands- searches docs content the commands- allows including and excluding "categories" of docs paths to search
Running node [audit-cli-documentation.js](http://_vscodecontentref_/1) both successfully audits both Core and Enterprise
Core templates use Core-specific frontmatter
Enterprise templates use Enterprise-specific frontmatter
Fixes audit-cli-documentation.js so that it parses commands dynamically from the CLI output.
Some commands () only return top-level help output, which the script had some difficulty with.That seems mostly resolved, but might rear again.
Add exclusion patterns for StackExchange sites to both production
and default link-checker configurations:
- *.stackexchange.com
- stackoverflow.com
- *.stackoverflow.com
These sites often block automated requests/bots, causing false
positive link validation failures in CI environments.
Add comprehensive documentation for maintainers on how to:
- Create releases in docs-tooling (automated)
- Manually distribute binaries to docs-v2 (required for private repo)
- Update workflow references when needed
This addresses the missing process documentation for link-checker
binary distribution between the two repositories.
feat(ci): update link-checker to v1.2.2 and add manual sync workflow
- Update pr-link-check.yml to use link-checker-v1.2.2 with latest fixes
- Add sync-link-checker-binary.yml for manual binary distribution
- Improvements in v1.2.2: base URL detection, anchor validation, JSON parsing
The v1.2.2 release fixes the Hugo base URL detection issue and
improves anchor link validation that was tested in this PR.
Addresses customer confusion where scaling CPU alone doesn't improve
compactor performance. Compactor concurrency scales based on memory
allocation, not CPU count, so both resources should be scaled together.
Closesinfluxdata/DAR#514
add related links
fix(clustered): correct anchor link in scale-cluster documentation
Fix broken internal anchor link from #rrecommended-scaling-strategies-per-component
to #recommended-scaling-strategies-per-component (removed extra 'r').
This was used to test the improved link-checker anchor validation functionality.
fix(clustered): correct anchor link in scale-cluster documentation
Fixes broken anchor link #rrecommended-scaling-strategies-per-component
to the correct #recommended-scaling-strategies-per-component
Jason Stirnaman
Scott Anderson
copilot-swe-agent[bot]
David Rusnak
David Rusnak
dependabot[bot]
Jason Stirnaman