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 Aug 15, 2023. It is now read-only.
The API for sharing dashboards with users/orgs returns different results depending on whether the dashboard was previously shared/not shared with the users/orgs. This should at least be clarified in the documentation.
This is observed both in PyLana and the API directly.
The text was updated successfully, but these errors were encountered:
Please let us know if you need clarification about the implemented behaviour. I would be a good candidate for such a clarification on slack, for e.g. :)
In principle:
Any sharing relates to either user or organization, not both at the same time.
In case of organization, that's an additive operation over multiple requests.
In case of user-to-user sharing, every time a request is received in the list of users to share the resource (e.g. dashboard) with the already existing state (if any) of user-to-user is cleared and the list which has been received last would prevail. So, user-to-user sharing is not an additive operation.
There is also the swagger documentation which - I believe - helps explaining it. Though, very briefly.
The API for sharing dashboards with users/orgs returns different results depending on whether the dashboard was previously shared/not shared with the users/orgs. This should at least be clarified in the documentation.
This is observed both in PyLana and the API directly.
The text was updated successfully, but these errors were encountered: