-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Change web get resources api response #10598
Conversation
b4e381d
to
ca46af9
Compare
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.
e
was mistakenly changed to an earlier commit, it should be left alone
0137417
to
ca46af9
Compare
ca46af9
to
051da5e
Compare
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.
Adding fields to our responses to the web UI won't break things, right?
@espadolini handling backwards compatibility for webassets has been very fuzzy to me. Backwards compat becomes a problem where there are mixed proxy versions: one older version can serve the old webassets, and an api call can go to a newer proxy returning a new response (and vice versa). I'm not sure how realistic it is for proxy versions to be mixed for long though, so with this assumption I did not supply fallbacks |
* Created a general listResourcesGetResponse as a consistent return value * Wrapped response in ^ object for resources that were not wrapped to accommodate future changes (dbs, desktops, kubes)
part of RFD 55
Description
listResourcesGetResponse
as a consistent return value