NibbleConfig lets each module declare and load its own configuration, instead of scattering configuration across config/*.exs files.

Usage

Modules requiring configuration can implement the NibbleConfig behaviour, and declare and use their own configuration:

defmodule MyApp.MyExternalService do
  use NibbleConfig, otp_app: :my_app

  @impl NibbleConfig
  def load_config(_ctx) do
    [
      api_key: System.fetch_env!("API_KEY"),
      # `Config.config_env/0` and `Config.config_target/0` are automatically
      # imported so you can refine the configuration based on the env and target.
      timeout: if(config_env() == :prod, do: 5_000, else: 60_000)
    ]
  end

  def call_service(path) do
    # Read the configuration
    api_key = config(:api_key)
    timeout = config(:timeout)

    HttpClient.get(path, api_key, timeout)
  end
end

They then need to be declared in config/runtime.exs:

NibbleConfig.new()
|> NibbleConfig.load_for(MyApp.MyExternalService)
|> NibbleConfig.load_for(MyApp.SomeOtherService)
|> NibbleConfig.apply_config()