-
Notifications
You must be signed in to change notification settings - Fork 0
Adds rake task variant for eliminating entire applications #1
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.
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
Conversation
The unsubscribe rake task, when passed two arguments, does not appear to actually delete any subscriptions. The exact reason for this is not obvious, but this is far from the only problem with the task: - the behavior when an app is provided but a queue name is omitted is surprising and potentially destructive - an application that uses multiple queues would require multiple runs of the task to fully decomission Solve both of these problems with a new code path that unsubscribes a single application in its entirety. This code path already existed, but was unreachable as a safeguard against shared applications conflicting across services.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| elsif app_key | ||
| manager.unsubscribe_app!(app_key) | ||
| else | ||
| manager = ::QueueBus::TaskManager.new(true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is clean! I like it
* Adds rake task variant for eliminating entire applications (#1) * Adds rake task variant for eliminating entire applications The unsubscribe rake task, when passed two arguments, does not appear to actually delete any subscriptions. The exact reason for this is not obvious, but this is far from the only problem with the task: - the behavior when an app is provided but a queue name is omitted is surprising and potentially destructive - an application that uses multiple queues would require multiple runs of the task to fully decomission Solve both of these problems with a new code path that unsubscribes a single application in its entirety. This code path already existed, but was unreachable as a safeguard against shared applications conflicting across services. * Bumps version to 0.13.3 * sadd deprecation fix for redis 4-8-1 * version update * changelog --------- Co-authored-by: Drew Long <48696687+aalong-tr@users.noreply.github.com> Co-authored-by: Shyamsunder Tadori <shyamsundertadori@Shyamsunders-MacBook-Pro-2.local>
* Adds rake task variant for eliminating entire applications (#1) * Adds rake task variant for eliminating entire applications The unsubscribe rake task, when passed two arguments, does not appear to actually delete any subscriptions. The exact reason for this is not obvious, but this is far from the only problem with the task: - the behavior when an app is provided but a queue name is omitted is surprising and potentially destructive - an application that uses multiple queues would require multiple runs of the task to fully decomission Solve both of these problems with a new code path that unsubscribes a single application in its entirety. This code path already existed, but was unreachable as a safeguard against shared applications conflicting across services. * Bumps version to 0.13.3 * pipelined deprecation fix * version update --------- Co-authored-by: Drew Long <48696687+aalong-tr@users.noreply.github.com> Co-authored-by: Shyamsunder Tadori <shyamsundertadori@Shyamsunders-MacBook-Pro-2.local>
* Adds rake task variant for eliminating entire applications (#1) * Adds rake task variant for eliminating entire applications The unsubscribe rake task, when passed two arguments, does not appear to actually delete any subscriptions. The exact reason for this is not obvious, but this is far from the only problem with the task: - the behavior when an app is provided but a queue name is omitted is surprising and potentially destructive - an application that uses multiple queues would require multiple runs of the task to fully decomission Solve both of these problems with a new code path that unsubscribes a single application in its entirety. This code path already existed, but was unreachable as a safeguard against shared applications conflicting across services. * Bumps version to 0.13.3 * setnx deprecation fix * version update --------- Co-authored-by: Drew Long <48696687+aalong-tr@users.noreply.github.com> Co-authored-by: Shyamsunder Tadori <shyamsundertadori@Shyamsunders-MacBook-Pro-2.local>
The unsubscribe rake task, when passed two arguments, does not appear to actually delete any subscriptions. The exact reason for this is not obvious, but this is far from the only problem with the task:
Solve both of these problems with a new code path that unsubscribes a single application in its entirety. This code path already existed, but was unreachable as a safeguard against shared applications conflicting across services.