This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
Watch Conditions, TriggerBindings, TriggerTemples #492
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.
This should fix issue #483 and work towards fixing issue #491
For created assets (tasks/pipelines/triggers) set ownerReference controller=true.
In turn they are properly watched and recreated if modified/deleted.
Add Watch for Condititions
Add Watch for TriggerBindings, TriggerTemplates...
It turns out the TriggerBindings and TriggerTemplates can't really be watched unless Kabanero is a cluster operator. The objects are created in
tekton-pipelines
namespace, but the operator env WATCH_NAMESPACE is scoped only tokabanero
. They don't get an ownerRef.Should probably be picked for 0.6