Feature Request: Support infrastructure-as-code workflows for promoting PostHog config between projects
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Feature request
Is your feature request related to a problem?
Teams with separate PostHog projects per environment (e.g., Dev, Staging, Prod) currently have to manually recreate feature flags, surveys, and cohorts across environments. This is error-prone and lacks traceability.
Describe the solution you'd like
An official way (via Terraform provider or CLI tool) to define PostHog config as code and promote it between environments in a repeatable, diffable way, starting with feature flags and surveys.
Describe alternatives you've considered
- Manually copying via the UI
- Using the API to script promotion
- Multi-project feature flags (useful, but limited in flexibility and visibility)
Additional context
From: https://posthoghelp.zendesk.com/agent/tickets/33924 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/35733)
Debug info
null
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
No repository file, test, or entry point is named. Start by determining whether the request belongs in a Terraform provider, a CLI tool, or both, and clarify the scope beyond feature flags and surveys. Done is not defined until the project agrees on a concrete promotion workflow and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- terraform
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100