Kafka has "configuration providers". Instead of putting a string literal in
your config, you put a reference to a value in an external source, and the
config provider fetches the config value from the source for you.
${file:/etc/secrets/tls.properties:keystore.password}
For sensitive option values like passwords and API keys, it means they don't
live in plain text in config.
${env:S3_SECRET_KEY}
There are built-in config providers to get config values from environment
variables and files, but it's a pluggable interface. Config providers are
available to get config values from K8s Secrets, HashiCorp Vault, AWS Secrets
Manager, Azure Key Vault, Google Secret Manager, etc.
${vault:path/to/secret:mypassword}
Has there ever been consideration of us adopting this idea in Flink? I think
it'd be super useful, but what do you think?
Kind regards
Dale
--
dalelane.co.uk