feat(provisioning): add sandbox/test mode for partner development
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Partners developing against the provisioning API create real PostHog accounts. Every test run creates real orgs, sends real welcome emails, and consumes real resources.
Options: (1) a test_mode flag that creates ephemeral accounts and suppresses welcome emails, (2) a separate test partner configuration, or (3) a staging environment. At minimum, suppressing welcome emails during testing would prevent the most confusing side effect.
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 at the provisioning API entry point and trace how partner test runs create accounts and send welcome emails. Compare the proposed test mode, separate partner configuration, and staging environment, with at least welcome-email suppression working for testing and real resources no longer being consumed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100