PNLP-7328: map reply_topic_key to kafka_replyTopic before kafka request #130
Conversation
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
|
ключевое изменение в SmartKitKafkaRequest |
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.
Новый функционал: задание header'а
kafka_replyTopicчерез указаниеreply_topic_keyвCommand.request_data(для акшнов, отнаследованных отCommandAction, этому соответствует итемrequest_data) в соответствие с маппингом из конфига перед отправкой запроса. Маппинг задаётся в конфиге так: в конфигеtemplate_config.ymlв полеreply_topicуказывается набор ключ-значений в форматеreply_topic_key: kafka_replyTopic.reply_topic_keyимеет приоритет надkafka_replyTopic, то есть в случае наличия обоих полей выберетсяreply_topic_key.