Schema Registry config generator scripts fail with provided values that contain an ampersand

[Danny02]

Name and Version

bitnami/schema-registry:7.8.0

What architecture are you using?

amd64

What steps will reproduce the bug?

1. use a SASL password with an ampersand &, e.g. SCHEMA_REGISTRY_KAFKA_SASL_PASSWORDS=my&password

What is the expected behavior?

config file /opt/bitnami/schema-registry/etc/schema-registry/schema-registry.properties contains

kafkastore.sasl.jaas.config = org.apache.kafka.common.security.scram.ScramLoginModule required username="user" password="my&password";

What do you see instead?

config file /opt/bitnami/schema-registry/etc/schema-registry/schema-registry.properties contains

kafkastore.sasl.jaas.config = org.apache.kafka.common.security.scram.ScramLoginModule required username="user" password="my# kafkastore.sasl.jaas.config =password";

Additional information

Function schema_registry_conf_set trys to set a key value pair in the config file by calling replace_in_file. The bug is that replace_in_file is using the value in a sed command that interprets the ampersand as a replacement.

I was able to workaround this issue by escaping the ampersand:

SCHEMA_REGISTRY_KAFKA_SASL_PASSWORDS='my\&password'

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.