You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the get_default_settings for API200 and 300 Logical Interconnect Group resource, either on Synergy or C7000, with the same syntax
Environment Details
OneView SDK Version: 3.1.0
OneView Appliance Version: 3.0
OneView Client API Version: 300
Ruby Version: 2.2.3
Platform: Windows
Steps to Reproduce
Use the methods, they are clear to use, but serve the same purpose even though they have different syntax.
Expected Result
The method gets defaults for something global, it should be a self method and could be implemented in api200 and just inherited by 300, with no need for repetition.
Actual Result
Currently there is an instance method on 200, and a self method on 300 synergy.
The text was updated successfully, but these errors were encountered:
jsmartt
changed the title
get_default_settings in API200 must be used is currently an instance method, when it should be a self method
get_default_settings in API200 must be used is currently an instance method, when it should be a class method
Jan 20, 2017
jsmartt
changed the title
get_default_settings in API200 must be used is currently an instance method, when it should be a class method
get_default_settings in API200 is currently an instance method, but it should be a class method
Jan 20, 2017
Scenario/Intent
Use the get_default_settings for API200 and 300 Logical Interconnect Group resource, either on Synergy or C7000, with the same syntax
Environment Details
Steps to Reproduce
Use the methods, they are clear to use, but serve the same purpose even though they have different syntax.
Expected Result
The method gets defaults for something global, it should be a self method and could be implemented in api200 and just inherited by 300, with no need for repetition.
Actual Result
Currently there is an instance method on 200, and a self method on 300 synergy.
The text was updated successfully, but these errors were encountered: