Recommended way to share/update pipeline configurations between projects?

[philip.scadding]

Hi Nik, welcome to the forums. Great questions!

1. It’s up to you really. Certainly, you won’t need to copy the files to each project, you will just need to upload a copy of the config to the site PipelineConfiguration entity. However, it may be beneficial to have a test project, with a config, so you can test changes outside of production.
   Personally I would be using git/GitHub where I would keep my source config and track the changes, then zip up the config from the repo and upload that.

2. Yeah, its a good point, perhaps that example is a bit distracting. You don’t need a projects/ bit in front of the name. You can optionally define a nested structure in the name, by separating it with /s. Doing so allows you to add additional folders after the root but before the main project folder.
   For example, you might wish to split your project folders out by client, or type of project: vfx_projects/my_vfx_project and game_projects/my_game_project.

3. Yes, that is correct, you will need to delete the PipelineConfiguration entity from your Shotgun site for that project. Maybe hold off on deleting the config on disk as well at first, so that you can check it all goes smoothly, otherwise, you can always restore the PipelineConfiguration back from the trash, and it should go back to how it was.
   3a. No, the projects should already have a tank_name if they were previously set up, clearing out the PipelineConfiguration entity should be all you need to do (assuming the site config is exactly the same in terms of schema). Though I recommend testing against the process with a dummy project just to make sure you feel comfortable with it.

4. If you upload the config, you should not need to set the descriptor. If you do it will take precedence over your uploaded config.

I hope that helps? You’ve probably seen these already, but I just thought I’d link them here as well:

Shared project configs

By default when you run the Toolkit advanced set up wizard for a project via Shotgun Desktop, you end up with a configuration created that is specific to that project. However, in certain setups you may wish to share your configuration with all your projects by default. To do this you will need to setup a site-level distributed config. Find the configuration you want to use. You can use the latest tk-config-default2 config (which is the default when using the setup wizard) or you can use a c…

Distributed config management workflow

I’ve seen the question come up a few times around how to test configuration changes and push them to production when using a distributed config setup. My personal recommendation would be to do the following: Assuming your project already has a “primary” PipelineConfiguration entity with an uploaded config, I would create a second one called dev. Set a dev descriptor to define a location to your config on disk. (If you haven’t got a config on disk you can download the primary config and unzi…