-
Notifications
You must be signed in to change notification settings - Fork 11.7k
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
Explore: Investigate options for QL/QH with missing or permissions controlled datasources #88001
Comments
cc: @diegoadams @ifrost - Feel free to add anything or debate the solutions |
I like it. It's clear what happened and gives the user options to recover. There used to be a similar pattern in alerts (I don't see it anymore though). You can see a screenshot in a proposal for this design doc. There's a box telling what happened and the user can choose from various options.
+1. CC @kylebrandt Do you know how easy it'd be to filter out resources based on permissions? I might be slow if we'd need to do a search and check for permissions for each query template's data source(s) 🤔 |
With Query Library and Query History, we store queries for a specific datasource to be used at a later time. However, datasources are not guaranteed to be permanent - they can be removed or the person can lose access to them. We need to think of what to do for these various perspectives, balancing UX concerns with security concerns.
Note: Deleting a datasource, then recreating it with the same UID won't apply here. The queries will always point to the datasource by UID, even if it is deleted and recreated after the query was saved.
Note 2: To make it easier to talk about, lets split queries in these features by temporary vs saved. Temporary queries are queries in query history that have not been starred. Saved queries are either starred queries in Query History or anything in Query Library.
Potential Scenarios
The text was updated successfully, but these errors were encountered: