-
Notifications
You must be signed in to change notification settings - Fork 141
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
Use the new universal methods for suspending/resuming a provider #434
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.
👍 LGTM
@slemrmartin are these methods still safe to use? |
@skateman yes, |
c1fccb3
to
cc4dd1b
Compare
Checked commit skateman@cc4dd1b with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
👍 LGTM. |
@skateman Since the goal is to try to have every PR include a related spec test perhaps you could update https://github.com/ManageIQ/manageiq-api/blob/master/spec/requests/providers_spec.rb to ensure the new methods are received. It shouldn't be too hard to add. Besides that 👍 LGTM |
@jvlcek there are already tests for this feature, I'm just changing the method to be called on the model. So I don't really understand what else should I test here, can you please clarify? |
@skateman Understood and agreed. I was just thinking that maybe an I'm OK with this PR as it is. JoeV |
Parent issue: ManageIQ/manageiq#17489
Depends on: ManageIQ/manageiq#17452
cc @slemrmartin
https://bugzilla.redhat.com/show_bug.cgi?id=1455145