Fixing Resource Labeling: Tying Infrastructure Metadata To Backstage With Ter...
summary
Shows how Backstage becomes the single source of truth for cloud labels by wiring the Backstage catalog API into Terraform via the terraform-provider-backstage, automatically injecting entity metadata into every plan so ownership, cost and compliance labels appear on every resource. Describes the initial rollout that broke deployments when Backstage was unavailable, then the fixes: a metadata wrapper module, provider retries and a Terraform remote state fallback that returns the last-known labels so plans succeed without drift and labels stay consistent.
AI-written summary · about
chapters (17)
- 0:00Fixing resource labels
- 2:12Resource labels for compliance
- 4:27Introduction
- 5:55Cloud Factory labeling
- 7:43Backstage for labeling
- 10:29Terraform to Backstage
- 11:53Terraform and Backstage API
- 13:19Backstage Terraform provider
- 14:47Dependency problem and fix
- 15:51Provider reliability
- 18:00Fallback mechanism
- 19:25Implementation and testing
- 20:27Terraform module walkthrough
- 21:54Automating label injection
- 22:15Actionable steps
- 23:19Resources and next steps
- 24:10Q&A
related talks
32mManaging Terraform resource drift using the GitOps method
35mBackstage: Restoring Order To Your Chaos
35mMisadventures with Terraform
24mGrowing Pains: Taming the Post-Startup Stage With Backstage
18mThe Path to Modern Infrastructure Automation [Abridged]
01h 01mClosing the documentation gap with Backstage.io
44mBridging Open Source Developer Platforms: Backstage Meets Coder
45mRETEX: Pitfalls and Traps with Terraform in the Enterprise