Skip to content

Conversation

@Raaghavcodes
Copy link
Contributor

@Raaghavcodes Raaghavcodes commented Jul 2, 2025

Issue

OLVM REST API responses for certain resource permissions including: cpuprofiles, vnicprofiles, and diskprofiles, were missing href(s) for a given resource id

Changes introduced with this PR

A change to the REST API forces all calls, to the REST API, for resource permissions to follow the same format. Changing the suggestedParentType to User.class changes the response for all resources to follow the pattern users/USER_ID/permissions/PERMISSION_ID

Are you the owner of the code you are sending in, or do you have permission of the owner?

Yes

Copy link
Member

@dupondje dupondje left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like a hack to get to the correct result?
Could you explain a bit more (with examples) what it changes, and why you changed it in this place.
Cause why is the suggestedParentType there otherwise?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants