Support Workload Identity Federation (WIF) for Snowflake
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Feature request
Describe the solution you'd like
https://docs.snowflake.com/en/user-guide/workload-identity-federation
https://www.snowflake.com/en/blog/simplify-authentication-workload-identity-federation/
Describe alternatives you've considered
Additional context
Request ticket: https://posthoghelp.zendesk.com/agent/tickets/56550 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/58183)
Debug info
- [x] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Snowflake Workload Identity Federation documentation linked in the issue and locate the repository's Snowflake authentication integration. No file, test, or entry point is identified in the payload, so the implementation scope needs clarification first. Done means PostHog can authenticate to Snowflake using WIF and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100