[Controls] Get Expensive Queries Setting With Internal User #155425
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Input Control
Input controls visualization
impact:critical
This issue should be addressed immediately due to a critical level of impact on the product.
loe:medium
Medium Level of Effort
Team:Presentation
Presentation Team for Dashboard, Input Controls, and Canvas
#155082 added a fallback to assume
allow_expensive_queries
is on when the user doesn't have themanage
permission required to check if it's on or not. The problem with this solution is that it could result in errors ifallow_expensive_queries
is off but the user doesn't have permission to check.Because even cloud / okta users are missing this
manage
permission, we should explore another way to get this information. One idea is to potentially use the internal user instead.If we do that, we should ensure that the endpoint is named properly, and doesn't take any post body or arguments.
The text was updated successfully, but these errors were encountered: