-
Notifications
You must be signed in to change notification settings - Fork 900
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
Add my_queue_name for ems_operations miq_requests #19739
Add my_queue_name for ems_operations miq_requests #19739
Conversation
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.
I'm wondering whether all MiqRequest classes belong to ems_operations. If that is the case, the same change would/should be applied to all MiqRequest classes? @gmcculloug What do you think?
Here is the list of classes that derive from
|
Yeah I was going through the obvious ones first, ones with a clear "source" object that I can use to get the queue_name from. But intend to go through all of the MiqRequestTask classes that have the ems_operations role. |
7e2bb77
to
6bc4102
Compare
89539ef
to
ec12b7f
Compare
@agrare As discussed can you add tests for the classes that have existing specs. Looks like that would include these:
I opened issue #19771 to create tests for the following classes that do not have tests today:
|
ec12b7f
to
197e18c
Compare
Checked commits agrare/manageiq@6cb7e9c~...197e18c with ruby 2.5.5, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0 |
@gmcculloug 👍 done |
Add a queue name for all of the ems_operations MiqRequest classes
#19543