[Core feature] Promote Workflows from Development to Production fast with cache

[clauk]

Motivation: Why do you think this is important?

The cache is not shared between Development and Production domain.
When the modelers finish development and plan to promote the workflow to production, the workflow needs a re-run even if some steps have been executed.

The ask here is to optimize this Development to Production process, to save compute resource and make iteration faster. Thanks!

Goal: What should the final outcome look like, ideally?

Development to Production process is fast, and avoid duplicate compute.

Describe alternatives you've considered

Ask everyone to stick with same domain for both development and production.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[welcome]

Thank you for opening your first issue here! 🛠

[eapolinario]

This is a great feature, unfortunately we don't have capacity to work on it at the moment. If you want to dive into it, please, tag me and we can talk about how to implement this.