KCL2 standard consumer registering as Fanout Consumer

[piratezoro]

In what version(s) of Spring Integration AWS are you seeing this issue?

3.0.2

Describe the bug

As per the new release there was a support introduced that enables standard consumer in KCL2 via PollingConfig

and adding a property :- spring.cloud.stream.kinesis.bindings..consumer.fanOut: false

Using this property ideally KCL2 should be a standard consumer and not a Fanout consumer. But when the service runs it is trying to registers the consumer as Fanout consumer.

Changes in accordance with the below commit :- spring-cloud/spring-cloud-stream-binder-aws-kinesis@895d69b

To Reproduce

Try to rollout the kinesis KCL2 standard consumer with the property
spring.cloud.stream.kinesis.bindings..consumer.fanOut: false

After the service boots up you can see the consumer registered on the kinesis stream.

Expected behavior

With polling config come's in , the consumer should not be registered on the kinesis stream.

[siddharthjain210]

this.config.retrievalConfig()

The above statement always returns new instance. The problem with the OnInit() and Start() in KclMessageDrivenChannelAdapter is that, 2 different instances were created.

I have addressed the fix, PR is raised, but the build has failed with unknown error. I couldn't re-run the build.
@artembilan : can you please take a look.

[piratezoro]

Hi @artembilan by when can we expect this changes in the spring cloud kinesis binder ?

[artembilan]

In a couple weeks. After next Spring Boot release: https://calendar.spring.io/