8000 fix(cdp): exclude internal_destinations from pipeline-add-on check by meikelmosby · Pull Request #33584 · PostHog/posthog · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix(cdp): exclude internal_destinations from pipeline-add-on check #33584

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

Conversation

meikelmosby
Copy link
Contributor
@meikelmosby meikelmosby commented Jun 12, 2025

Important

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Problem

  1. internal_destinations should not be part of the pipeline error check. this will also resolve this issue for now https://posthog.slack.com/archives/C06GG249PR6/p1749671833470969
  2. we currently have hogfunctions with sub-template-ids created in the frontend. as we are querying the templates by parent-id this leads to errors

Changes

  • exclude internal_destination from data-pipelines-addon-check
  • add migration to rename the existing sub-template-ids to their parent-ids

How did you test this code?

  • added test

Copy link
Contributor
@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

Modified data pipeline add-on check logic to exclude internal destinations from requiring premium Data Pipelines feature, ensuring core PostHog functionality remains accessible regardless of subscription status.

  • Excluded internal_destination type from data-pipelines-addon-check in posthog/api/hog_function.py
  • Added comprehensive lifecycle tests in posthog/api/test/test_hog_function.py to verify internal destinations work without Data Pipelines add-on
  • Improved template handling robustness by only applying template code/schema when template exists
  • Fixed potential error where code attempted to access properties of non-existent template

2 files reviewed, no comments
Edit PR Review Bot Settings | Greptile

@meikelmosby meikelmosby requested a review from benjackwhite June 12, 2025 08:58
@meikelmosby meikelmosby requested a review from benjackwhite June 12, 2025 11:06
Copy link
Contributor
@benjackwhite benjackwhite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

meant to click request changes

@meikelmosby meikelmosby requested a review from benjackwhite June 12, 2025 11:32
@meikelmosby meikelmosby merged commit d6b86f5 into master Jun 12, 2025
98 checks passed
@meikelmosby meikelmosby deleted the fix/meikel/error-tracking-should-not-be-part-of-data-pipelines-addon-check branch June 12, 2025 14:30
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.

2 participants
0