TechDocs: Use lowercase entity kind, namespace and name in URLs
See original GitHub issueFeature Suggestion
When you open a TechDocs page like https://demo.backstage.io/docs/default/Component/backstage
The entity namespace (e.g. default) and kind (e.g. Component) and name should be in lowercase.
Possible Implementation
Look at /catalog plugin for inspiration.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
TechDocs How-To guides - Backstage.io
Follow the detailed instructions for using cloud storage in TechDocs. ... with case-insensitive entity triplet paths (e.g. /docs/namespace/kind/name whereas ...
Read more >Extend the Ed-Fi ODS / API - Student Transportation Example
This example uses MetaEd to generate extended artifacts and documentation. ... Folders are generally named after their entity type.
Read more >Installation parameters - Technical Documentation For IFS ...
the installer will use the "enabled" value of the parameter ifsappproxy.accessLog and "1" of the global.replicas since that was passed as a "--set"...
Read more >Tanzu Application Platform v1.1 | VMware Docs
Find the catalog locations and their entities' namespace/kind/name. 637. Use the TechDocs CLI to generate and publish TechDocs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

We took a look at this and here’s our proposed path forward…
techdocs-cli) that will copy any objects in storage from case-sensitive triplet paths to lower-case triplet paths.PublisherBasesignature (perhaps calledmigrateDocsCaseor similar) which handles the logic on a per-storage provider basis. (We may want to publish this in TechDocs common, followed by thetechdocs-clifirst, to allow time to advertise the change to the community and resolve any issues in the migration command)publishanddocsRoutermethods to lowercase the entity triplet at read/write time. In the release notes in this PR, we’ll advise those who use external storage/generation solutions to run thetechdocs-climigration command prior to rolling out the release. (As noted previously in this issue, folks running local generation will be unaffected)One additional annoyance: MacOS’s file system is case insensitive by default, so testing this locally on a Mac is challenging.
Closure of this potentially also closes https://github.com/backstage/backstage/issues/2269