This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
Fix ImageChange triggers not being set in DeploymentConfig when resource fragments are used. #1794
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related StackOverlow post: https://stackoverflow.com/questions/60375063
This seems to be a regression since we introduced sidecar containers support. For applying
ImageChange triggers we have to check which containers are main application containers and
which are sidecars. Well, we do that but when we don't set any
defaultApplicationContainerName
when the sidecar option is disabled. It seemed like a bug introduced me during implementation.
Sample project for testing: https://github.com/r0haaaan/fmp-openshift-sample-with-fragments
If you test on master, you can see in generated resources that
ImageChange
triggers are not being applied. But on this patch, they are being applied correctly.