An Easier Path to a Rich Catalog
summary
Claims a writable catalog where metadata edits update entities immediately via a fragments API that stores small JSON objects in a new database table and a processor that merges them into Backstage entities. Demonstrates an entity decorator UI and inline editing for annotations and owners, plus a PagerDuty plugin that fetches service IDs via API, cutting time-to-change from days to seconds. Case studies include customers such as Twilio; feature is proprietary (not open source) but exposes an API for export.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:51What does Roadie do
- 1:13The problem
- 2:28Open a pull request
- 7:02The happy path
- 7:34The provider path
- 9:16Possible solutions
- 10:55Our solution
- 15:16Backend
- 16:49Backstage QA
- 17:00Entity Inspector
- 18:25Vendor Lockin
- 18:57API
- 20:37Ownership
- 22:23Questions
related talks
29mAutomatically generate Backstage entity descriptors for easy adoption
39mHow We Scaled Catalog Ingestion to Hundreds of Thousands of Entities
32mIs Backstage for me?
23mUnlocking the Catalog: Providing a Platform CLI for Backstage
49mA Front Row Seat to Backstage Adoption
09mBackstage Beyond Engineering Teams: Can We Deliver Value to Other...
10mLightning Talk: We Built a Unified AI Asset Catalog in Backstage
26mCan Affordance Catalogs power up your Dev Portal?