Question 1

How do I add a custom configuration provider in ZeroCfg?

Accepted Answer

Implement the Provider interface with Type and Provide methods, then pass an instance to zfg.Parse. The Provide method should return maps of found and unknown keys based on the awaited parameter, using the conv function for value conversion.

Question 2

ZeroCfg vs Viper: which is better for Go configuration?

Accepted Answer

ZeroCfg is ideal if you prefer a minimal, flag-like API with strict boilerplate reduction. Viper offers more features like multiple file formats, remote sources, and hot reloading, but with increased complexity and less emphasis on compile-time safety.

Question 3

Can ZeroCfg handle environment variables in Kubernetes or Docker?

Accepted Answer

Yes, the env source automatically transforms dotted keys (e.g., 'db.user') to uppercase with underscores (DB_USER), making it compatible with standard container orchestration practices without extra configuration.

Question 4

How does ZeroCfg protect secrets from being logged?

Accepted Answer

By using zfg.Secret() when defining options, their values are replaced with '<secret>' in the output of zfg.Show(), preventing accidental disclosure in debug outputs or logs.

Question 5

What happens if my YAML file has extra keys not defined in code?

Accepted Answer

zfg.Parse will return an error by default for unknown keys, but you can use zfg.IsUnknown to ignore them. Note that the env source doesn't trigger this to avoid false positives from system variables.

Question 6

Does ZeroCfg support hot reloading of configuration files?

Accepted Answer

No, ZeroCfg does not support hot reloading natively; configuration is parsed once at startup. For dynamic updates, you would need to implement custom logic or use a different library that includes this feature.

zerocfg

What is zerocfg?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions