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
{{ message }}
This repository has been archived by the owner on Mar 11, 2021. It is now read-only.
Do we wanna enhance the existing Collaborators API Endpoint?
Or, do we wanna add a more generic search endpoint for searching role associations for any resource? Search/Filter assignees for a specific resource, by name/username/email...
I would go for the second one.
The text was updated successfully, but these errors were encountered:
@sbose78 Will the endpoint be used for the determination of privileges in order for users to perform an action, or just for informational/management purposes?
The second option sounds like it could also lend itself to allowing a cleaner implementation of the "My Spaces" vs "Shared Spaces" distinction that is now made on the Spaces page. These buttons allow the table to toggle between showing Spaces that the logged in user owns vs ones that they are collaborators on (and do not own). Currently there's a bit of ugly logic that was implemented in order to get at the "collaborates but doesn't own" set:
The front-end would need support for
Search Space Collaborators
in our backend API.https://openshift.io/openshiftio/Openshift_io/plan/detail/942
Things to be considered:
Search/Filter assignees for a specific resource, by name/username/email...
I would go for the second one.
The text was updated successfully, but these errors were encountered: