Wildcards for GitHub auto-discovery, [Video] Creating a Backstage Best-practices Scorecard, Single-entity retrievals for Tech Docs Checks.
You can now specify paths with wildcards for Roadie to discover entities in GitHub. There’s a new video tutorial for helping you define Backstage Best-practices through Scorecards. Additionally, you can now trigger Checks retrievals for specific entities and we revamped the Checks Table UI.
If you have multiple repos with existing
catalog-info.yaml files, it can be handy to be able to discover them all at once instead of having to go through them one by one. You can now do it using wildcards like this one:
The same applies if you’re using monorepos. You’ll need to import all of your monorepos as following:
For more information, check out our GitHub auto-discovery guide.
David has put together some tutorials for creating a checks to keep track of your organization’s Backstage practices.
There are a number of tutorials ready:
- Ensure mandatory metadata is set
- Ensure the spec.lifecycle is valid
- Ensure the Component type is valid
- Ensure a group owner is present in each catalog-info file
- Ensure the GitHub annotation is set in the catalog-info file
- Ensure catalog-info labels are being used correctly
You can now run the retrievals of checks for specific entities. Th is makes Tech Docs more effective in managing resources and giving you relevant data on demand. To use this feature, go to Tech Insights > Data Sources, select the relevant Data Source and then run the fetching on the specified entity.
Based on customer feedback, we’ve revamped the Checks and the Data Sources tables to make it easier to navigate. You can now hide/show columns. Check it out and let us know what you think!