Hi there,
Is it possible to implement a Git-style fork and rebase pattern with workshops and Foundry branches?
We have a complex setup where we have dozens of workshop products (base product) which we install to multiple client environments via marketplace.
We install in bootstrap mode and then afterwards, these workshops need adjustments (drifts) after installation for changes such as addition extra columns to tables, adjusting variables or adding in extra embedded workshops. This steps are done manually in the normal no-code workshop flow.
When we later update the base workshop in marketplace, we want to deploy the updated version to the pre-existing client installations. When this happens, as with updated bootsrapped products, we lose the drifts of those installations, and then we need to manually re-do the drifts that we did earlier. This currently significantly slows down our development speed and increases our deployment risk.
Ideally there would be a way we would use Foundry branching to achieve this. We would want the live version of the workshop installed for the client to be on the master branch. Ideally we could then deploy an update of the product from marketplace to a Foundry branch as opposed to master, so the drifts would be unaffected. Then we could merge this branch to the production one, bringing in the changes from the base product but also keeping the drifts that were done after it was first installed.
Thanks,
Solomon