Our Backstage setup is too hard to keep updated

That’s a common pain point with Backstage setups as they grow.

A few typical reasons they become hard to keep updated:

• Too many manually maintained YAMLs for entities, plugins, and integrations
• Duplicate config across environments
• Plugin sprawl where upgrades break assumptions
• Scattered ownership so no one knows who updates what
• Customizations baked into the core app instead of being modular

Ways to make it easier:

1. Centralize and generate config

   • Use templates or code generation for repeated entity definitions
   • Keep environment-specific values in one place

2. Reduce manual catalog maintenance

   • Prefer discovery-based ingestion where possible
   • Use Git-based source of truth with automation checks

3. Modularize plugins and extensions

   • Isolate custom features so plugin upgrades are less painful

4. Add validation and CI

   • Lint catalog files, validate schemas, and run Backstage checks in CI before merge

5. Standardize ownership

   • Make each catalog entity and plugin clearly owned by a team

6. Track upgrade work explicitly

   • Maintain a plugin/version inventory and schedule periodic upgrades

If you want, I can help you with one of these:

• a Backstage maintenance checklist
• a migration plan to reduce manual upkeep
• or a review of your current Backstage architecture if you share how it’s set up.