Skip to content
This repository was archived by the owner on May 14, 2025. It is now read-only.
This repository was archived by the owner on May 14, 2025. It is now read-only.

Cannot use custom bindings names from Spring Cloud Config #6117

Open
@CEDDM

Description

@CEDDM

Description:
I'm using SCDF with Kafka on Kubernetes platform and I would like to use Spring Cloud Config for application configuration, including Kafka configurations with topic names.
In our company we have 1 SCDF with 1 Kafka cluster shared for multiple environments. Each environment has its own SCC server.

So our streams are prefixed with env code (like dev-mystream) and we pass the SCC server URL in deploy command. Then I would like the apps to use env specific topic names (also prefixed with env code like dev-mytopic) in the env specific SCC configuration file for the app.
But it seems that SCDF/Skipper server passes bindings names as arguments to the pod in the command line (spring.cloud.stream.bindings.input.destination and spring.cloud.stream.bindings.output.destination) with classic value <stream name>.<app label> and my SCC configuration is just ignored.

We should have a way to put all the apps configuration in Spring Cloud Config.

Release versions:

  • SCDF 2.11.5
  • Apps use Spring Boot 3

Custom apps:
No

Steps to reproduce:
Use SCDF with Spring Cloud Config in a tiktok stream for example with specific topic names configured in SCC.
After deploying the stream, you will see the bindings names in SCC are not taking into account.

Screenshots:

Additional context:
Today as a workaround, I pass the bindings in the deploy command.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status/need-triageTeam needs to triage and take a first look

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions