[Feature Request] Leverage Env Vars in YML Files

The YML files are great for checking configuration into source control, but some information (like the Schema Registry URLs and bootstrap servers, for example) I’d rather keep out of source control and set with environment variables similar to Docker Compose.

default.yml

runners:
    default: "local"
    config:
        lambda:
            deploy: null
            credentials:
                type: "default"
            awsRegion: null
            enabled: false
        kubernetes:
            namespace: "default"
            context: null
            deletePodAfterCompletion: true
            cpu: "1"
            memory: "512M"
            timeoutMs: 300000
            image:
                registry: "docker.io"
                image: "adevinta/zoe-core"
                tag: null
        local:
            enabled: true
storage: null
secrets: null
expressions: {}
clusters:
    default:
        registry: ${SCHEMA_REGISTRY}
        props:
            bootstrap.servers: ${BOOTSTRAP_SERVERS}
            key.deserializer: "org.apache.kafka.common.serialization.StringDeserializer"
            value.deserializer: "io.confluent.kafka.serializers.KafkaAvroDeserializer"
            key.serializer: "org.apache.kafka.common.serialization.StringSerializer"
            value.serializer: "io.confluent.kafka.serializers.KafkaAvroSerializer"
        groups: {}
        topics:
            topic1:
                name: topic1-long-name

default.env

SCHEMA_REGISTRY=http://localhost:8081
BOOTSTRAP_SERVERS=localhost:9092

[wlezzar]

Hi @rsaltrelli : ) . Have you checked out this? https://adevinta.github.io/zoe/configuration/chain/ . You can use the ZOE_CONFIG_OVERRIDE environment variable to override part of zoe’s configuration. Does it suit your use case? If not can you explain me in a bit more detail your use case?

[wlezzar]

@rsaltrelli @G3zz The feature is now available on the latest version v0.26.0