Wondering how you’re all dealing with asset management across multiple Orchestrator instances (dev --> test --> prod).
For example, if multiple processes are being created, some of which require NEW assets, others require UPDATED assets, and the devs perform those changes on the dev Orchestrator server, we know that pushing a new process to the dev server is as easy as clicking “Publish”.
Often a release manager will grab that package and physically drop it onto test instance of Orchestrator, and then eventually move it to prod.
However… what is your process for bringing the right assets along from Dev --> Test --> Prod?
How do you keep track of which ones are new vs. updates vs. deletes, etc and make sure the right changes occur in upper env?