Skip to content

[eas-cli] Add integrations:posthog:connect (core provision flow)#3836

Draft
gwdp wants to merge 1 commit into
gwdp/posthog-m3a-graphqlfrom
gwdp/posthog-m3b-connect
Draft

[eas-cli] Add integrations:posthog:connect (core provision flow)#3836
gwdp wants to merge 1 commit into
gwdp/posthog-m3a-graphqlfrom
gwdp/posthog-m3b-connect

Conversation

@gwdp

@gwdp gwdp commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Why

Connect an Expo app to PostHog in one command — provisions the project and writes the SDK env vars. Core provision flow; feature prompts / SDK install / config-plugin deferred.

How

  • Region via --region or prompt; required in non-interactive
  • Reuses an existing connection/project (provisioning is irreversible)
  • Handles the existing-user dead-end
  • Writes EXPO_PUBLIC_POSTHOG_API_KEY + EXPO_PUBLIC_POSTHOG_HOST to Production/Preview/Development

Test Plan

  • CI — 7 unit tests
  • Live run needs the universe PostHog backend deployed

@gwdp gwdp force-pushed the gwdp/posthog-m3b-connect branch from 0a4e058 to 9ac957d Compare June 10, 2026 06:57
@gwdp gwdp force-pushed the gwdp/posthog-m3a-graphql branch from bf35e3a to 49a8f7b Compare June 12, 2026 05:09
@gwdp gwdp force-pushed the gwdp/posthog-m3b-connect branch from 9ac957d to 7ddf04d Compare June 12, 2026 05:09
@gwdp gwdp force-pushed the gwdp/posthog-m3b-connect branch from 7ddf04d to 2467434 Compare June 12, 2026 05:30
@github-actions

Copy link
Copy Markdown

✅ Thank you for adding the changelog entry!

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.

1 participant