Skip to content

Feat/enable snowflake private key auth - #17

Closed
woogakoki wants to merge 81 commits into
upstream-masterfrom
feat/enable_snowflake_private_key_auth
Closed

woogakoki wants to merge 81 commits into
upstream-masterfrom
feat/enable_snowflake_private_key_auth

Conversation

@woogakoki

Copy link
Copy Markdown

What type of PR is this?

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

Description

How is this tested?

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

Related Tickets & Documents

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

github-actions Bot and others added 30 commits July 1, 2025 00:43
In commits fc1e1f7 and e44fcdb a new Selector option was added to
alerts, which may be "first", "min" or "max".  This migration sets the
default to "first" for existing alerts.
* Make NULL value visible
* Make the representation of NULL value configurable
* use display-as-null css class for null-value styling
* Use 12-column layout for dashboard grid

Set minSizeX, minSizeY for widgets to 2 since a value of 1 breaks all
assumptions of the UI layout.

Migration provide transition from 6 to 12 columns for all widgets.

* Restyled by prettier
* Added support for Google Oauth Scheme Override (through environment variable)

* Refactoring

* Refactoring

* Applied formatting

* Refactoring

* Refactoring

* Updated comment for `GOOGLE_OAUTH_SCHEME_OVERRIDE` variable

* Updated comment for `GOOGLE_OAUTH_SCHEME_OVERRIDE` variable

* Removed duplication of url_for function

---------

Co-authored-by: kostiantyn-dementiev-op <kostiantyn.dementiev@observepoint.com>
* diff locations ignore

* add logging message

* Processing Location is not specified
As with other query runners, do not show system tables in the schema list.
* add private_key auth method

* fix casing

* fix private_key parsing

* use params and add optional pwd

* use private_key_b64

* add file option

* remove __contains__

* fix pem pwd

* fix lint issues

* fix black

---------

Co-authored-by: Tsuneo Yoshioka <yoshiokatsuneo@gmail.com>
* Relocate [tool.poetry] to [project] section
* Add dependencies section to [project]
* Format authors and maintainers as objects
…edash#7521)

This prevents duplicate entries in the schema list.  Materialized views are the
only table-like object not found information_schema. Also ensure that the schema
and table found in information_schema is accessible by the current user.
…h#7527)

* Update jql.py (jira datasource) to use jira api v3 updated.

* fix spaces in blank lines

* Add condition for empty "fields"

---------

Co-authored-by: Artem Safiiulin <asafiiulin@cloudlinux.com>
Co-authored-by: Tsuneo Yoshioka <yoshiokatsuneo@gmail.com>
* Fix too many history.replaceState() error on Safari

* fix restyled error by running prettier for client/app/services/location.js
inytar and others added 3 commits February 25, 2026 13:36
The default JSON.parse used by axios does not work well with big numbers
and will trunctate them. To fix this we replace the parser used by axios
by a JSON parser that does work with big numbers.
if user is None:
return logout_and_redirect_to_index()

return redirect(next_path or url_for("redash.index", org_slug=org_slug), code=302)


def extract_name(email):

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Static Code Analysis Risk: Identified pii in python code

Detected the parameter name(s) email inside extract_name

Severity: Info ℹ️
Status: Open 🔴

References:

  1. https://wiki.playtika.com/spaces/SEC/pages/672278106/PII

More details:

🌻 View in Arnica

For license findings, please review our legal policy: https://wiki.playtika.com/pages/viewpage.action?spaceKey=LEG&title=Open+Source+Code+Usage+Guidelines


Take action by replying with an [arnica] command 💬

Actions

Use [arnica] or [a] to interact with the Arnica bot to acknowledge or dismiss code risks.

To acknowledge the finding as a valid code risk: [arnica] ack <acknowledge additional details>

To dismiss the risk with a reason: [arnica] dismiss <fp|accept|capacity> <dismissal reason>

Examples

  • [arnica] ack This is a valid risk and I'm looking into it

  • [arnica] dismiss fp Dismissed - Risk Not Accurate: (i.e. False Positive)

  • [arnica] dismiss accept Dismiss - Risk Accepted: Allow the risk to exist in the system

  • [arnica] dismiss capacity Dismiss - No Capacity: This will need to wait for a future sprint

Comment thread poetry.lock
typing-extensions = ">=4.5.0"

[[package]]
name = "ldap3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

License Risk: ldap3@2.9.1 uses LGPL-3.0

LGPL-3.0 violates license policy.

Severity: Medium ⚠️
Status: Open 🔴

License Details:

  1. LGPL-3.0

More details:

🌻 View in Arnica

For license findings, please review our legal policy: https://wiki.playtika.com/pages/viewpage.action?spaceKey=LEG&title=Open+Source+Code+Usage+Guidelines


Take action by replying with an [arnica] command 💬

Actions

Use [arnica] or [a] to interact with the Arnica bot to acknowledge or dismiss code risks.

To acknowledge the finding as a valid code risk: [arnica] ack <acknowledge additional details>

To dismiss the risk with a reason: [arnica] dismiss <fp|accept|capacity> <dismissal reason>

Examples

  • [arnica] ack This is a valid risk and I'm looking into it

  • [arnica] dismiss fp Dismissed - Risk Not Accurate: (i.e. False Positive)

  • [arnica] dismiss accept Dismiss - Risk Accepted: Allow the risk to exist in the system

  • [arnica] dismiss capacity Dismiss - No Capacity: This will need to wait for a future sprint

Comment thread poetry.lock
Comment thread poetry.lock
redis = ["limits[redis]"]

[[package]]
name = "flask-login"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependency Risk: flask-login@0.6.0 has 8 transitive vulnerabilities

🏗️ Recreate the poetry.lock file (run poetry update) to mitigate 100% of critical and high risks (100% of all)

🩹 Upgrade to 0.6.3 (patch version) and recreate the poetry.lock file (run poetry update) to mitigate 100% of critical and high risks (114% of all)

Severity: High 🚨
Status: Open 🔴

More details:

🌻 View in Arnica

For license findings, please review our legal policy: https://wiki.playtika.com/pages/viewpage.action?spaceKey=LEG&title=Open+Source+Code+Usage+Guidelines


Take action by replying with an [arnica] command 💬

Actions

Use [arnica] or [a] to interact with the Arnica bot to acknowledge or dismiss code risks.

To acknowledge the finding as a valid code risk: [arnica] ack <acknowledge additional details>

To dismiss the risk with a reason: [arnica] dismiss <fp|accept|capacity> <dismissal reason>

Examples

  • [arnica] ack This is a valid risk and I'm looking into it

  • [arnica] dismiss fp Dismissed - Risk Not Accurate: (i.e. False Positive)

  • [arnica] dismiss accept Dismiss - Risk Accepted: Allow the risk to exist in the system

  • [arnica] dismiss capacity Dismiss - No Capacity: This will need to wait for a future sprint

Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
{file = "pandas-1.3.4-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:9707bdc1ea9639c886b4d3be6e2a45812c1ac0c2080f94c31b71c9fa35556f9b"},
{file = "pandas-1.3.4-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:c2f44425594ae85e119459bb5abb0748d76ef01d9c08583a667e3339e134218e"},
{file = "pandas-1.3.4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:372d72a3d8a5f2dbaf566a5fa5fa7f230842ac80f29a931fb4b071502cf86b9a"},
{file = "pandas-1.3.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:d99d2350adb7

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

License Risk: restrictedpython@7.3 uses ZPL-2.1

ZPL-2.1 violates license policy.

Severity: High 🚨
Status: Open 🔴

License Details:

  1. ZPL-2.1

More details:

🌻 View in Arnica

For license findings, please review our legal policy: https://wiki.playtika.com/pages/viewpage.action?spaceKey=LEG&title=Open+Source+Code+Usage+Guidelines


Take action by replying with an [arnica] command 💬

Actions

Use [arnica] or [a] to interact with the Arnica bot to acknowledge or dismiss code risks.

To acknowledge the finding as a valid code risk: [arnica] ack <acknowledge additional details>

To dismiss the risk with a reason: [arnica] dismiss <fp|accept|capacity> <dismissal reason>

Examples

  • [arnica] ack This is a valid risk and I'm looking into it

  • [arnica] dismiss fp Dismissed - Risk Not Accurate: (i.e. False Positive)

  • [arnica] dismiss accept Dismiss - Risk Accepted: Allow the risk to exist in the system

  • [arnica] dismiss capacity Dismiss - No Capacity: This will need to wait for a future sprint

Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
Comment thread poetry.lock
graph = ["gremlinpython (==3.3.4)"]

[[package]]
name = "certifi"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

License Risk: certifi@2025.6.15 uses MPL-2.0

MPL-2.0 violates license policy.

Severity: Medium ⚠️
Status: Open 🔴

License Details:

  1. MPL-2.0

More details:

🌻 View in Arnica

For license findings, please review our legal policy: https://wiki.playtika.com/pages/viewpage.action?spaceKey=LEG&title=Open+Source+Code+Usage+Guidelines


Take action by replying with an [arnica] command 💬

Actions

Use [arnica] or [a] to interact with the Arnica bot to acknowledge or dismiss code risks.

To acknowledge the finding as a valid code risk: [arnica] ack <acknowledge additional details>

To dismiss the risk with a reason: [arnica] dismiss <fp|accept|capacity> <dismissal reason>

Examples

  • [arnica] ack This is a valid risk and I'm looking into it

  • [arnica] dismiss fp Dismissed - Risk Not Accurate: (i.e. False Positive)

  • [arnica] dismiss accept Dismiss - Risk Accepted: Allow the risk to exist in the system

  • [arnica] dismiss capacity Dismiss - No Capacity: This will need to wait for a future sprint

Comment thread poetry.lock
{file = "pandas-1.3.4-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:9707bdc1ea9639c886b4d3be6e2a45812c1ac0c2080f94c31b71c9fa35556f9b"},
{file = "pandas-1.3.4-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:c2f44425594ae85e119459bb5abb0748d76ef01d9c08583a667e3339e134218e"},
{file = "pandas-1.3.4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:372d72a3d8a5f2dbaf566a5fa5fa7f230842ac80f29a931fb4b071502cf86b9a"},
{file = "pandas-1.3.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:d99d2350adb7

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

License Risk: zope-event@5.0 uses ZPL-2.1

ZPL-2.1 violates license policy.

Severity: High 🚨
Status: Open 🔴

License Details:

  1. ZPL-2.1

More details:

🌻 View in Arnica

For license findings, please review our legal policy: https://wiki.playtika.com/pages/viewpage.action?spaceKey=LEG&title=Open+Source+Code+Usage+Guidelines


Take action by replying with an [arnica] command 💬

Actions

Use [arnica] or [a] to interact with the Arnica bot to acknowledge or dismiss code risks.

To acknowledge the finding as a valid code risk: [arnica] ack <acknowledge additional details>

To dismiss the risk with a reason: [arnica] dismiss <fp|accept|capacity> <dismissal reason>

Examples

  • [arnica] ack This is a valid risk and I'm looking into it

  • [arnica] dismiss fp Dismissed - Risk Not Accurate: (i.e. False Positive)

  • [arnica] dismiss accept Dismiss - Risk Accepted: Allow the risk to exist in the system

  • [arnica] dismiss capacity Dismiss - No Capacity: This will need to wait for a future sprint

Comment thread poetry.lock
{file = "pandas-1.3.4-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:9707bdc1ea9639c886b4d3be6e2a45812c1ac0c2080f94c31b71c9fa35556f9b"},
{file = "pandas-1.3.4-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:c2f44425594ae85e119459bb5abb0748d76ef01d9c08583a667e3339e134218e"},
{file = "pandas-1.3.4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:372d72a3d8a5f2dbaf566a5fa5fa7f230842ac80f29a931fb4b071502cf86b9a"},
{file = "pandas-1.3.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:d99d2350adb7

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

License Risk: zope-interface@7.2 uses ZPL-2.1

ZPL-2.1 violates license policy.

Severity: High 🚨
Status: Open 🔴

License Details:

  1. ZPL-2.1

More details:

🌻 View in Arnica

For license findings, please review our legal policy: https://wiki.playtika.com/pages/viewpage.action?spaceKey=LEG&title=Open+Source+Code+Usage+Guidelines


Take action by replying with an [arnica] command 💬

Actions

Use [arnica] or [a] to interact with the Arnica bot to acknowledge or dismiss code risks.

To acknowledge the finding as a valid code risk: [arnica] ack <acknowledge additional details>

To dismiss the risk with a reason: [arnica] dismiss <fp|accept|capacity> <dismissal reason>

Examples

  • [arnica] ack This is a valid risk and I'm looking into it

  • [arnica] dismiss fp Dismissed - Risk Not Accurate: (i.e. False Positive)

  • [arnica] dismiss accept Dismiss - Risk Accepted: Allow the risk to exist in the system

  • [arnica] dismiss capacity Dismiss - No Capacity: This will need to wait for a future sprint

Comment thread yarn.lock
Comment thread viz-lib/yarn.lock
@woogakoki
woogakoki requested review from a team and inytar February 25, 2026 13:21
@woogakoki
woogakoki changed the base branch from master to upstream-master February 25, 2026 13:57
@inytar

inytar commented Apr 23, 2026

Copy link
Copy Markdown

@koki is this still valid? Or do we close this?

@inytar

inytar commented May 4, 2026

Copy link
Copy Markdown

@koki is this something we can close? And related, what is now the correct branch for us to work on? Could you make sure that's also the github "main" branch?

@woogakoki woogakoki closed this May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.