Kafka triggers are gone - #850
Merged
Merged
Conversation
Removed in v2.18.2, but the page still walked people through configuring one and the intro still promised three trigger types. A short note stands where the section was, rather than nothing. People will search for this, and anyone who had a Kafka trigger needs to know it became a disabled webhook trigger rather than disappearing. Self-hosters get the environment variable warning from the changelog, since that one bites on upgrade. The Kafka input state section in the jobs docs goes too, along with the link that pointed at it.
josephjclark
approved these changes
Sep 14, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Short Description
Kafka triggers were removed in v2.18.2, but the docs still explain how to configure one. This replaces that section with a short note and drops the Kafka input state section.
Details
The page intro promised three trigger types and the section below it walked through connecting a cluster, complete with a screenshot and a "known sharp edges" list written as an ongoing beta.
I left a note rather than deleting outright. People will search for this, and anyone who had a Kafka trigger needs to know it became a disabled webhook trigger rather than vanishing. Self-hosters get the
KAFKA_TRIGGERS_ENABLEDwarning, since that one bites on upgrade.Removal shipped in OpenFn/lightning 2.18.2 on 2 Sep, per its changelog.
Note this touches the same file as #849, though the two apply cleanly together.
AI Usage
Please disclose how you've used AI in this work (it's cool, we just want to know!):
You can read more details in our Responsible AI Policy