I’m just toying with the idea of having a single shared pipeline config for the studio that is able to reference a templates.yml stored in each project folder for per-project overrides (eg client delivery templates). It would be great to be able to do this as it lessens the likelyhood of requiring a…

Hey Patrick – That all makes sense. And you’re not alone in wanting this functionality; @kporangehat asks pretty much the exact same question in this post . And I hear what you’re saying about the risks – perfectly coordinating the schema and templates is always a challenge; this definitely complica…

Ah, I’ve just remembered about the " example_template_hook.py" core hook which I think would cover my use-case for what I’m trying to do. I’m still interested to hear other thoughts on the above though! Cheers p.

Actually, on second look, that template hook is only for app settings. I don’t think it would allow me to evaluate a template via hook at runtime via tk.templates[‘some_dynamic_template’] method. So, the question remains, how to define templates outside templates.yml?

It looks like the “pipeline_configuration_init.py” core hook initialises prior to templates.yml, so that might be a place where I can define the env var pointing to the project path. The problem is I can’t see where I can find what project is being loaded. There is the TANK_CURRENT_PC environment …

Hey Patrick - I added this line to templates.yml and it worked: include: "${INCLUDE_PATH}/test.yml" so we definitely do support env vars in template includes. As for when to set the env var, pipeline_configuration_init is the right place, and it looks like you can get to the project name via sel…

Oh, and as for an example of using includes in templates.yml, you can see one here: [image] Refactoring templates Pipeline Integrations Hey Mois – moved this one over to the Pipeline Integrations category so we can get more Toolkit eyes on it. One thing you might want to…

Thanks Tanaz, So I have the project name, is, etc. I don’t unfortunately have the roots. There’s a self._storage_roots but it’s not got a value. I assume because I’m using distributed configs? Are the roots available from this point in the process? p.

Hi Patrick – I’m not sure what you’d want the storage roots for – is your intention to store the included files in the same location as your production files? It actually leads me to a few other questions: if you’re using distributed configs, where would these included files live? Where are you inc…

Yes that’s right. I’m looking to be able to have a single pipeline configuration for the entire studio, but where the studio defaults need adjusted on a per-project basis, instead of having a seperate pipeline config, I would impliment overrides in files within the project folder. I appreciate that…

Hi Patrick, Couldn’t you use the same configuration every where and set the values you want to customize per project in environment variables?

Possibly. I’ve not tried instantating new templates from strings on the fly before though. I can probably do something along those lines but as a point of principle I’d prefer to keep all my path resolution within sg templates. Thanks for the suggestion anyway!

Template.yml per-project includes

Pipeline Integrations

Topic		Replies	Views
Am I alone? Single pipeline config with per-project overrides? Pipeline Integrations	26	2966	May 6, 2023
Recommended way to share/update pipeline configurations between projects? Pipeline Integrations	16	4561	January 29, 2024
Hierarchical includes in environment config files Pipeline Integrations	3	1741	March 17, 2020
Getting the pipeline configuration name from within pipeline_configuration_init.py? Pipeline Integrations	14	2060	February 19, 2021
Dynamic Pipeline Configurations Pipeline Integrations	7	2280	September 22, 2023

Template.yml per-project includes

Related topics