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

Solution Verified - Updated -

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.

Environment

OpenShift Enterprise 3.0.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.