We have a project that uses the old Duct with Component, were we use bindings to bind env vars from the env https://github.com/akvo/akvo-lumen/blob/develop/backend/src/akvo/lumen/main.clj#L16 & https://github.com/akvo/akvo-lumen/blob/develop/backend/src/akvo/lumen/config.clj#L21

How do you go about this in the new Duct with Integrant?

@kardan just to clarify, are you asking how to grab ENV vars in Duct with Integrant?

or how to map from external env vars to an internal naming scheme for vars (in a single map)?

if the former, you do it as part of the config map: :some-key {:some-var #duct/env ["EXTERNAL_NAME" <Some Coercing Function> :or "some-default"]}

e.g., :some-component-key {:db-url #duct/env ["DB_URL" Str :or "some-default-value"]}

if you want to build a map of all env vars that you can pass around as a whole, you could simply repeat the pattern above: :my-env-map {:a #duct/env [..] :b #duct/env [..] :c #duct/env [..] ..} and then pass the env map to other components through refs: :some-other-component {:envs #ig/ref :my-env-map}

https://github.com/duct-framework/core/blob/master/src/duct/core/env.clj#L23

does that answer your question?

Ah, yes! Thanks

Maybe I’m just slow after a long day. But this what I was trying to understand while staring at the screen 🙂