-
Notifications
You must be signed in to change notification settings - Fork 897
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
Expose attach/detach method for volume #14289
Expose attach/detach method for volume #14289
Conversation
c808552
to
5802c2a
Compare
5802c2a
to
0f11a5b
Compare
Checked commit andyvesel@0f11a5b with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
Looks good to me 👍 |
@@ -10,5 +10,7 @@ class MiqAeServiceCloudVolume < MiqAeServiceModelBase | |||
expose :cloud_volume_backups, :association => true | |||
expose :cloud_volume_snapshots, :association => true | |||
expose :attachments, :association => true | |||
expose :attach_volume, :override_return => nil | |||
expose :detach_volume, :override_return => nil |
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.
Is it possible to return a success or failure status of some kind? The user will have no indication if the method was successful if we always return nil
.
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.
Thanks for comment. These model methods raise an error on failure or nothing meaningful on success. Would :override_return => true
work or should we update methods body to return true/false (or something better)?
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 think we are good it the backing method raises an error. Thanks.
Expose
attach
anddetach
methods for Cloud Volume