Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hog CDP Megaissue #22833

Open
28 of 65 tasks
benjackwhite opened this issue Jun 10, 2024 · 0 comments
Open
28 of 65 tasks

Hog CDP Megaissue #22833

benjackwhite opened this issue Jun 10, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@benjackwhite
Copy link
Contributor

benjackwhite commented Jun 10, 2024

Hog CDP Megaissue

Closed beta release

Open beta release (feature preview)

  • Get LogEntries connected
  • Templating helpers - find a relevant event and give autocomplete suggestions for both string and code inputs
  • Get AppMetrics connected
  • Native oauth integration (needed for a lot of destinations, e.g. salesforce)
  • Show function status in the list view and alert when disabled
  • Test autocapture work (likely works but lets just triple check)

General release

  • Secret management
  • Fix activity log
  • Test event data from real events
  • Event throughput estimation - show a rough estimate of how many matching events will trigger with warnings
  • Ensure that the billing guard is in place for data pipelines addon
  • Indicate when oauth integration scopes need refreshing
  • Fix groups stuff as that is broken now...

Non-blocking ideas / work

  • Linked destinations for actions
  • Fix channel selector to save the name as well if possible
  • Idea: generalise the way to modify the event / person properties so it isn't implemented per plugin
  • Ensure optional properties work as expected person?.properties?.email
  • Expose posthog.capture method as a minimum so we can have more control over these use cases
  • Create a sleep/timer service
  • Remove old action matching bytecodes from postgres
  • Indicate specifically if the underlying template has been updated since it was forked (allowing people to know there are "updates" available
  • Pull the "leader" into its own deployment

Plugin parity

List of existing destinations and whether we have a corresponding Hog solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant