Configu v1.0.0 has officially landed, and we’re thrilled. After months of hard work, countless coffee-fueled nights, and more YAML than we’d care to admit, the Configu product has hit its first major milestone.
Let’s dive into what this release means for you, how to get started, and why we think it’s going to change how you think about software configuration management forever.
What’s New in Configu v1.0.0?
Here’s the TL;DR: Configu now packs dynamic expressions, smarter validation tools, a leaner, meaner CLI, and so much more. Let’s break down the highlights:
ConfigExpressions – Next-Level Dynamic Configuration
Why settle for static configuration when you can have dynamic, reusable values? With ConfigExpressions, you can now use string interpolation, arithmetic, and even libraries like lodash, validator.js, and Zod to level up your config game.
For example:
keys:
GREETING:
const: 'Hello, ${name}!'
test: 'expect($.value).to.be.a("string")'
It’s like your configs just got their first gym membership.
Validation, the Smart Way
Say goodbye to rigid “types” and hello to the new test property. Use tools like Chai or validator.js to enforce rules dynamically. For instance:
keys:
ENABLE_FEATURE:
test: validator.isBoolean($.storedValue)
MY_KEY:
test: '$.configs.ENABLE_FEATURE.value ? expect($.value).to.be.a("string") : true'
This isn’t just validation; it’s next-gen configurability.
CLI Glow-Up
The CLI has undergone a complete makeover:
- 1000% faster (yes, we measured).
- Now built on the lightweight Clipanion framework.
- Dynamic module loading for smaller installs.
- Improved Windows support and compatibility across platforms.
Oh, and installation? It’s as easy as pie:
macOS/Linux:
curl https://files.configu.com/cli/install.sh | sh
Windows:
irm https://files.configu.com/cli/install.ps1 | iex
Auto-Detected Defaults
Your .configu
file just got smarter. Place it anywhere in your project tree, and Configu’s CLI will find it like a truffle pig sniffing out treasures.
Getting Started with Configu v1.0.0
Ready to dive in? Here’s how:
- Install the CLI (instructions above).
- Write your first
.cfgu
file with dynamic ConfigExpressions and validation.
Using a previous version of Configu and want to switch: here’s a v1 Migration Guide.
Why Configu?
Configu is more than just another configuration tool. It’s a mission to eliminate the messy, error-prone world of config files and turn configuration management into a joyride. Whether you’re scaling microservices or just tired of wrangling .env files, Configu’s here to help.
A Quick Example
Here’s a taste of Configu in action:
$schema: https://json-schema.org/draft/2020-12/schema-cfgu
keys:
NODE_ENV:
description: Defines the environment in which the application runs
enum:
- development
- production
- test
default: development
LOG_LEVEL:
description: Defines the level of logs to be recorded
enum:
- error
- warn
- info
- debug
default: info
SERVICE_ENDPOINT:
description: Defines the endpoint for the service
test: validator.isURL($.value)
required: true
AWS_REGION:
description: Defines the AWS region for the service
enum:
- eu-west-1
- us-east-1
- us-west-1
default: us-east-1
Run it through the CLI with:
configu eval --schema './config.cfgu.yaml' | configu export --format 'k8s-config-map'
Boom. Your configs, validated and ready to roll.
We Hope You Enjoy the New Release!
We couldn’t have done this without our amazing community. Every PR, every Discord message, every “what if Configu could…” has brought us to this moment. Thank you.
Now go forth and build something amazing.
Have any questions? Join our Discord channel, or schedule a demo.