Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Selectively stop flows in case of emergencies #39

Open
Luscha opened this issue Oct 26, 2023 · 2 comments
Open

Selectively stop flows in case of emergencies #39

Luscha opened this issue Oct 26, 2023 · 2 comments
Labels
operations priority/high
Milestone
Infrastructure 2....

Comments

@Luscha
Copy link
Contributor

Luscha commented Oct 26, 2023 •
edited by sseppi
Loading

As an Open Data Hub maintainer i want to to selectively stop flows in case of emergencies
@sseppi sseppi changed the title As an Open Data Hub maintainer i want to to selectively stop flows in case of emergencies Selectively stop flows in case of emergencies Oct 30, 2023
@sseppi
Copy link

sseppi commented Oct 30, 2023 •
edited
Loading

@Luscha this issue should be discussed in the next meeting to better define the priority. Is this issue related also to the issue #40 ?

@sseppi sseppi added the question Further information is requested label Oct 30, 2023
@sseppi sseppi added this to the 1st Service on Production milestone Oct 30, 2023
@Luscha
Copy link
Contributor Author

Luscha commented Nov 6, 2023

It's not related to issue #40.
This issue is about stoping a flow at an arbitraty step (writer, transformer, ...) (letting the queues buffer the message we don't manage), #40 is about replaying messages we already processed

@sseppi sseppi removed the question Further information is requested label Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
operations priority/high
Projects
None yet
Milestone
Infrastructure 2.0 Production Ready
Development

No branches or pull requests
2 participants
@sseppi @Luscha