Defining reuseable parts of template yamls | Backstage | Page 1

smoky birch Jul 10, 2024, 8:52 PM

#

I'm looking to reuse certain properties of my templates in multiple templates. Mostly fields like certain dropdowns that are hard coded values.

ornate python Jul 10, 2024, 9:31 PM

#

Hi @smoky birch, have you tried this? https://backstage.io/docs/features/software-templates/input-examples#use-placeholders-to-reference-remote-files

Input Examples | Backstage Software Catalog and Developer Platform

Some examples to use in your template

smoky birch Jul 11, 2024, 1:31 PM

#

Hi @ornate python , thanks for the response. Unfortunately, I'm using local files :/

I haven't yet understood why local files inside the backstage repo aren't supported in certain things. I like backstage holding my templates, because it's the only thing that uses it.

ornate python Jul 11, 2024, 1:40 PM

#

At its core Backstage is an aggregtor of data and not the source of truth. Following that frame of reference not supporting local files beyond local development (or has somewhat incomplete support) perhaps makes more sense.

smoky birch Jul 11, 2024, 1:45 PM

#

So is it common practice to store these templates in some kind of random template repo?

#

Looks like I'm abandoning local files, and will just reference the github file inside the backstage repo 🤷

#

And this works perfectly when I do that! Thanks so much for your help!

#Defining reuseable parts of template yamls