Make snowflake log to stdout

[verhovsky]

By default, snowflake-sdk logs to a snowflake.log file in the current directory

https://github.com/snowflakedb/snowflake-connector-nodejs/blob/v2.3.6/lib/logger/node.js#L17

https://github.com/snowflakedb/snowflake-connector-nodejs/blob/da6afd13b5997f8c8c405edc83a576422568062e/lib/logger/node.js#L71-L83

This is probably not what we want, so this makes it log just to STDOUT. The other options are to log to a different file, disable logging entirely by logging to /dev/null or with logLevel: "OFF", or log to both a file and STDOUT, or log to stderr by passing /dev/stderr (would have to check this actually works, unfortunately we can't pass "STDERR" here, even though it's been requested).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
pipedream-docs-redirect-do-not-edit	Ignored		Mar 31, 2026 7:38am

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d1733111-46a7-4a76-8f4d-a0a4523530da

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch boris/update-snowflake

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible