feat(temporal-worker): Add steps to trigger deployment #17881
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We trigger a temporal worker deploy when changes are detected under posthog/temporal or posthog/batch_exports. This may change in the future, but we'll update this workflow when that happens.
danielxnj
reviewed
Oct 10, 2023
danielxnj
approved these changes
Oct 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Temporal workers should be deployed separately from the PostHog monolith for a few of reasons:
Changes
We trigger a temporal worker deploy when changes are detected under posthog/temporal or posthog/batch_exports. This may change in the future, but we'll update this workflow when that happens.
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
How did you test this code?