Orchestration groups - Granular behaviour for different types of update
Adding more granular control to the behaviour orchestration groups depending on types of updates would improve the feature greatly.
For example, specifying different behaviour for different types of updates - customers probably don't want to run pre-scripts and post-scripts or even potentially any orchestration for definition updates, whereas they might want to for other types of updates
any advanced on this? this is extremly necessary for avoiding that it applies to definition updates.
Ryan Hathaway commented
Really need a way to either ignore Orchestration groups on a deployment, so we can do that for defintions, or a way to only enact the orchestration group on types of updates as stated in the request.