Kafka trigger parameterization issues

[nachoge]

Hello,

We've been using Kafka triggers for a long time. We have never had to have a different environment-based parameterization for any of the enum values. Right now we need to have different ones for BrokerProtocol.

Development should be BrokerProtocol.SASLPLAINTEXT
while Production should be BrokerProtocol.SASLSSL

Brokers can be parameterized!

I'm not able to find any way to achieve that! Is there a way? which one -without having to refactor source code on build time a k a: code replacements-

To me seems very limiting not to be able to parameterize ALL OF THEM. Am I missing something?

Using a Constant Class defining
public static final BrokerProtocol BUILD_KAFKA_BROKERS_PROTOCOL_PLAIN=BrokerProtocol.SASLPLAINTEXT;
is neither an option in order to made code replacements -ugly- but in a centralized place

Thanks in advance

@KafkaTrigger(
name = String,
topic = String,
brokerList=String,
protocol=BrokerProtocol <---------------------------- NOT Parameretizable!
consumerGroup=String,
username=String,
password=String,
dataType=String,
authenticationMode=BrokerAuthenticationMode, <---------------------------- NOT Parameretizable!
cardinality=Cardinality, <---------------------------- NOT Parameretizable!
sslCertificateLocation=String,
sslCaLocation=String
)

[muleycharge]

Related to #389

Does anybody have any work arounds for this? AuthenticationMode, and Protocol vary in our application across environments and trying to figure out how to get around this. Also, Dev envs have an empty value for Password, Username, SchemaRegistryUsername, and SchemaRegistryPassword which makes the library throw an error instead of just ignoring those settings.

[frenchyjef]

Same here... we want to parametrize these values in our app.settings.json because the values are different between environments we deploy to.