You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
In KEP52 the proposal is, the give the user the opportunity to customize subscriptions for a given Keptn Integration.
Supporting this use case, the distributor needs to be triggered to update its current subscriptions to the desired state.
In order to do so, the distributor listens for and reacts to the general purpose event (e.g. sh.keptn.event.subscription.changed, defined in #4437 ) which holds the current subscription information for a particular keptn integration and updates its subscriptions accordingly.
ℹ️ In order to implement the above feature, also a distributor which is running on a remote execution plane needs to be able to receive event other than *.triggered. (done in #4498)
Acceptance Criteria
Keptn integration can be used to update its subscriptions dynamically.
Distributor is able to create subscriptions with different filters each
Solution is backwards compatible
Definition of Done
existing integration test is enhanced to test this functionality
johannes-b
changed the title
(WIP) Distributor: Consume events that signal a subscription change
Distributor: Consume events that signal a subscription change
Jul 6, 2021
Action Item
In KEP52 the proposal is, the give the user the opportunity to customize subscriptions for a given Keptn Integration.
Supporting this use case, the distributor needs to be triggered to update its current subscriptions to the desired state.
In order to do so, the distributor listens for and reacts to the general purpose event (e.g.
sh.keptn.event.subscription.changed
, defined in #4437 ) which holds the current subscription information for a particular keptn integration and updates its subscriptions accordingly.ℹ️ In order to implement the above feature, also a distributor which is running on a remote execution plane needs to be able to receive event other than
*.triggered
. (done in #4498)Acceptance Criteria
Definition of Done
Dependencies
#4437
#4498
The text was updated successfully, but these errors were encountered: