Add impersonation option in trino datasource

[kimsehwan96]

What type of PR is this?

• Refactor
• Feature
• Bug Fix
• New Query Runner (Data Source)
• New Alert Destination
• Other

Description

Add user impersonation support for Trino data source.

Background

Trino supports user impersonation, which allows query auditing and fine-grained access control by passing the actual user identity to Trino instead of a shared service account.

Changes

• Added impersonation option to enable/disable user impersonation
• Added impersonationField option to select which user attribute to use for impersonation:
  • email: Uses the user's email (default)
  • name: Uses the user's name
• For ApiUser, falls back to name since API keys don't have an associated email

Configuration

Both options are available under "Additional Settings" in the data source configuration.

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

1. Trino datasource with disabled impersonation and query 2. Trino datasource with impersonation as email and query 2. Trino datasource with impersonation as name and query

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

[cubic-dev-ai]

No issues found across 1 file

[yoshiokatsuneo]

I have not tested it.

But I believe I can approve it as:

• The PR author looks tested well.
• The changed code looks good.
• There is no test failure.

[yoshiokatsuneo]

@kimsehwan96

Thank you for your contribution with detailed description !
As I believe the PR makes redash more useful, I just approved and merged.

[kimsehwan96]

@yoshiokatsuneo Thank you for the fast review and merge!
I think Presto could use this feature as well (since Trino is a forked version of Presto), but I haven't used Presto myself, so I'll leave that to someone else who's more familiar with it.