Hi Joe – I’m afraid there isn’t anything like that.
tank cache_apps doesn’t modify your config, but it relies on the version in the config to determine what to download, ie it doesn’t download the latest.
You could always create a dummy config solely for the purpose of downloading the latest bundles – you can safely run
tank updates on it without breaking your production pipeline.
I’ll mention also, if you have multiple pipeline configs using a shared core, their apps/engines will also be downloaded to the same place. For example, if you have two projects sharing the same
tk-core that are on, say, v0.11.15 and v0.12.0 of
tk-multi-workfiles2, respectively, in the shared core location you’ll have:
So with this, you could store all versions of the bundles together – both for your production config and your sandbox one. Note that shared cores have different behavior between their attached projects’ core versions and app/engine versions – there is only ever one copy of
tk-core in a shared core, and updating it for one project updates it for all, but multiple versions of app/engines are stored, and whatever versions are specified in a project’s config will be used. More on shared cores here.