Why ConfigChange trigger is added when no trigger is defined in deployment config.

Issue

• We updated our OpenShift Enterprise to version 3.0.2. One of the new features is that when I define a deployment config, if I don't define a trigger OpenShift by default adds the ConfigChange trigger. Is there any method to avoid this? We prefer to deploy manually only.

• ConfigChange trigger when no trigger in DC

• How to avoid default trigger that is added when no trigger is defined in deployment config.