[Question] How to manually register a binding in code

Open
#3,140 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, kafka, spring
Domain
backend, distributed-systems

Research direction

The issue provides only a Spring Cloud Stream YAML configuration for the cpeResult function and Kafka binding; it names no source file, test, or entry point. Start by locating the Java-side binding-registration API and compare it with the shown cpeResult-in-0 configuration. Done means a common module can register the binding without each consuming service repeating the configuration.

Written by the indexing model from the issue text.

Description

spring:
    cloud:
        function:
             definition: cpeResult
        stream:
          bindings:
             cpeResult-in-0:
                     binder: kafka-manage
                     destination: mqtt_cpecommunication_kafka_topic
                     group: ucc_${spring.application.name}

Yaml Config Above.
I just want to register it in code not config.
Because I am writing the logic of a common module that needs to be dependent on many other microservices, I hope that other services will not need to display the configuration when referencing this module

Dominant language
Java
Stars
1.1k
Forks
646
Avg merge
2d 3h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-cloud/spring-cloud-stream

All issues in spring-cloud/spring-cloud-stream

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.