A lightweight configuration management tool that keeps local config files up-to-date using data from etcd, Consul, or other backends.
confd is a lightweight configuration management tool that manages local application configuration files using templates and data from backends like etcd, Consul, or environment variables. It solves the problem of keeping configuration files synchronized across distributed systems and enables dynamic configuration updates without manual intervention.
DevOps engineers, SREs, and developers managing microservices or distributed systems who need dynamic, centralized configuration management without heavy orchestration tools.
Developers choose confd for its simplicity, support for multiple backends, and ability to automatically update and reload configurations, making it a reliable and focused alternative to heavier configuration management systems.
Manage local application configuration files using templates and data from etcd or consul
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates with etcd, Consul, DynamoDB, Redis, Vault, ZooKeeper, AWS SSM Parameter Store, and environment variables, offering versatility for diverse infrastructure setups as highlighted in the README.
Uses Go templates to generate configuration files from backend data, allowing dynamic and customizable management without heavy dependencies.
Monitors backend changes and updates local files automatically, ensuring configuration stays current and reducing manual intervention.
Can trigger application reloads or restarts upon config changes, facilitating seamless updates without downtime.
The cleanup phase involves merging etcd backends and removing template functions like cget, causing migration headaches and requiring version pinning for stability.
Removal of encryption-related template functions due to unmaintained dependencies reduces built-in security capabilities, forcing reliance on external solutions.
Relies on older channels like IRC and mailing lists, with documentation that may lag behind the transitional state, potentially hindering support.