-
Notifications
You must be signed in to change notification settings - Fork 202
4.0.0 is generating ImageChange triggers in the DeploymentConfig #1578
Comments
@mojsha : just looked , I think flag is still there : fabric8-maven-plugin/plugin/src/main/java/io/fabric8/maven/plugin/mojo/build/ResourceMojo.java Lines 264 to 265 in 3a17aa4
Are you facing this issue when using resource fragments? I think we missed flag here while refactoring: Lines 146 to 156 in 3a17aa4
|
@rohanKanojia I am not sure since I haven't followed the code changes, but yes I am using a DC resource fragments and in the existing version (3.5.42) I don't get this ImageChangeTrigger added. |
Are you talking about |
@rohanKanojia Yes precisely.The consequence is the extract I added in the first post, i.e. "automatic: true". |
…loymentConfig Fixed my mistake while refactoring Converters into Enrichers
…loymentConfig Fixed my mistake while refactoring Converters into Enrichers
…loymentConfig Fixed my mistake while refactoring Converters into Enrichers
…nfig Fixed my mistake while refactoring Converters into Enrichers
Description
It seems like 4.0.0 has reverted to generating ImageChange triggers for OpenShift DeploymentConfig objects with the automatic field set to true, e.g.
This needs to be fixed, and the flag to disable this re-introduced.
f-m-p version :
4.0.0
Kubernetes / OpenShift setup and version :
3.10
If it's a bug, how to reproduce :
mvn fabric8:resource fabric8:build fabric8:apply on a project with a DeploymentConfig
@rohanKanojia
The text was updated successfully, but these errors were encountered: