omniconf
omniconf copied to clipboard
grammarly
Configuration library for Clojure that favors explicitness
Building under Clojure 1.11.1 produces the following warning: ``` WARNING: parse-boolean already refers to: #'clojure.core/parse-boolean in namespace: omniconf.core, being replaced by: #'omniconf.core/parse-boolean ```
I really like the idea behind omniconf, and have been wanting something like this that would make it possible to unify configuration from files, env variables, and command line arguments....
Hello, I have a perhaps rare but not unheard of usecase where I need to read a configuration file with custom reader macros (like integrant's `ig/ref`). Therefore I've provided a...
I have a config paramter that stores the HDFS location of a file. The parameter has HDFS IP, port and the file location, something like `hdfs://172.21.1.11:54310/schema/schema.txt`. Since IPs and ports...
Question marks are not allowed in environment variables but are valid keywords in clojure. We should escape question mark to something (maybe `_Q_`) and use that as the variable name.
* **Version**: 0.2.5 * **Type**: Query/Clarification to understand if there is a better way to define multi-valued configs * **Summary**: Need to define a validated configuration for parameters that may...
This change fixes a critical bug when running on EKS, in which omniconf assumes the node role instead of ServiceAccount's pod role. I.e: this change adds `aws-java-sdk-sts` dependency, allowing omniconf...
