-
Notifications
You must be signed in to change notification settings - Fork 74
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
Make disconnect_storage a no-op #272
Conversation
Pull Request Test Coverage Report for Build 1733
💛 - Coveralls |
Pull Request Test Coverage Report for Build 1767
💛 - Coveralls |
def self.miq_src_vm_disconnect_storage(obj, _inputs) | ||
event_object_from_workspace(obj).src_vm_disconnect_storage | ||
def self.miq_src_vm_disconnect_storage(_obj, _inputs) | ||
# Method has been deprecated and will be removed in a future version |
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 don't think we are using the word "deprecated" correctly here. Would be more accurate to say that the src_vm_disconnect_storage
logic has been removed and this method remains for backwards compatibility with older Automate models and/or users overriding DestroyVM_Task_Complete
and USER_REMOVE_VM_FINISHED
event instances. See ManageIQ/manageiq-content#472
The "will be removed in a future version" is right on. 👍
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.
That's a good point, updated
6c10eba
to
05c125d
Compare
@@ -33,7 +33,7 @@ def src_vm_destroy_all_snapshots | |||
end | |||
|
|||
def src_vm_disconnect_storage | |||
ar_method { @object.src_vm_disconnect_storage } | |||
# Method has been deprecated and will be removed in a future version |
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 comment needs the same change.
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.
👍 done
Disconnect_storage no longer needs to be called from the event_handler and can be removed. Making these no-ops for backport.
05c125d
to
b0236ac
Compare
Some comments on commit agrare@b0236ac spec/service_models/miq_ae_service_ems_event_spec.rb
|
Checked commit agrare@b0236ac with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
Okay @gmcculloug this is ready |
@miq-bot add_label blocker |
@agrare can you add the hammer/yes and gaprindashvili/yes labels if this can and should be backported. |
Make disconnect_storage a no-op (cherry picked from commit d9dcef8) https://bugzilla.redhat.com/show_bug.cgi?id=1654436
Gaprindashvili backport details:
|
Make disconnect_storage a no-op (cherry picked from commit d9dcef8) https://bugzilla.redhat.com/show_bug.cgi?id=1644770
Hammer backport details:
|
Disconnect_storage no longer needs to be called from the event_handler
and can be removed. Making these no-ops for backport.
https://bugzilla.redhat.com/show_bug.cgi?id=1644770