Configuration Normalization in Golang Services

[Azhovan (Jabar Asadi)]

A trailing space in an environment variable can break a deployment.

I just added the Config Transformers to Rigging.

Config values come in as strings (env/files), and they’re often messy. One extra space, weird casing, or a trailing slash can cause annoying bugs. But validation is (and should be) strict.

So something like `" PROD "` can fail `oneof:dev,staging,prod` even though it’s obvious what you meant.

Config Transformers in Rigging run before validation, so you get a nice place to normalize once in a single spot

Want to read more:
GitHub: GitHub - Azhovan/rigging: A typed, observable, policy-driven configuration system for Go services.
Docs: rigging/docs/quick-start.md at main · Azhovan/rigging · GitHub

[Gohar]

@Azhovan

A trailing space in an environment variable can break a deployment.

I just added the Config Transformers to Rigging.

Config values come in as strings (env/files), and they’re often messy. One extra space, weird casing, or a trailing slash can cause annoying bugs. But validation is (and should be) strict.

So something like " PROD " can fail oneof:dev,staging,prod even though it’s obvious what you meant.

Config Transformers i

Config values come as strings, and they’re often messy. A small thing like " PROD " can fail strict validation like oneof:dev,staging,prod just because of extra spaces or casing. Config Transformers fix this by cleaning the value first — trimming spaces, fixing casing, etc. So validation stays strict, but small formatting mistakes don’t break your deployment.