I usually check-in triggers in the codebase as "Stopped" because I don't want anything to run for the first time without any supervision in the new environment. From experience, this is the preferred approach from DevOps support engineers.
I would like for this tool to have the following option when deploying:
1- Stop any "Started" triggers.
2- Deploy triggers from the codebase; new triggers will be deployed as "Stopped".
3- Start just the triggers that were "Started" before the deployment, e.g. those that got stopped at #1.
This is incredibly useful when deploying into production, as you might have to run post-steps after a release before any trigger can be started.
I usually check-in triggers in the codebase as "Stopped" because I don't want anything to run for the first time without any supervision in the new environment. From experience, this is the preferred approach from DevOps support engineers.
I would like for this tool to have the following option when deploying: 1- Stop any "Started" triggers. 2- Deploy triggers from the codebase; new triggers will be deployed as "Stopped". 3- Start just the triggers that were "Started" before the deployment, e.g. those that got stopped at #1.
This is incredibly useful when deploying into production, as you might have to run post-steps after a release before any trigger can be started.