Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[API300] Why is Switch the only resource that directly implements #set_scope_uris? #146

Closed
tmiotto opened this issue Jan 30, 2017 · 1 comment
Closed

[API300] Why is Switch the only resource that directly implements #set_scope_uris? #146

tmiotto opened this issue Jan 30, 2017 · 1 comment
Assignees
@ricardogpsf
Labels
API300 C7000 unexpected_behavior

Comments

@tmiotto
Copy link
Contributor

tmiotto commented Jan 30, 2017

Scenario/Intent

I'm trying to understand why API300 Switch has the #set_scope_uris, but other resources don't, like, server_hardware, enclosure...

I know it is the only patch operation it supports right now but, if we are trying to have some consistency, or every single patch operation has to be implemented as a separate method, or the API300 Switch should implement a #patch method.

Environment Details

  • OneView SDK Version: 3.1.0
  • OneView Client API Version: 300
@tmiotto tmiotto changed the title Why do Switch is the only resource that directly implements #set_scope_uris? [API300] Why do Switch is the only resource that directly implements #set_scope_uris? Jan 30, 2017
@ricardogpsf
Copy link
Member

With the #133 some helper methods (add_scope, remove_scope, replace_scopes) were added to Enclosure and ServerHardware too.
And with #147 the helper methods were added to LogicalSwitch too.

@jsmartt jsmartt changed the title [API300] Why do Switch is the only resource that directly implements #set_scope_uris? [API300] Why is Switch the only resource that directly implements #set_scope_uris? Feb 7, 2017
@ricardogpsf ricardogpsf self-assigned this Feb 21, 2017
@ricardogpsf ricardogpsf mentioned this issue Feb 21, 2017
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ricardogpsf ricardogpsf

Labels
API300 C7000 unexpected_behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ricardogpsf @tmiotto