Port 12483 Update blueprint for consumer groups in ports kafka integration #1971
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
…o-ports-kafka-integration
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
hadar-co
approved these changes
Jan 22, 2025
…o-ports-kafka-integration
hadar-co
deleted the
PORT-12483-add-support-for-consumer-groups-to-ports-kafka-integration
branch
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.
Description
This PR simplifies the representation of consumer group members by modifying the "members" field in the consumer group blueprint. Previously, this field was an array of objects containing detailed member information. To streamline the data and reduce complexity, the "members" field now includes only the
client_idof each member.Why this change?
The previous structure with full member objects was overwhelming and unnecessary for the intended use case. After discussions, it was agreed that the
client_idis sufficient to represent members effectively.Updated docs pages
Please also include the path for the updated docs
/build-your-software-catalog/sync-data-to-catalog/event-processing/kafka#consumer-group)