1. Obvious

  1. Obvious

  1. Obvious

What is Obvious config?

What is Obvious config?

Organize configuration to make it easier to understand by people and systems.

Organize configuration to make it easier to understand by people and systems.

Why Obvious config?

Why Obvious config?

  1. Easily understand which config goes where becuase secrets and parameters are well organized. The alternative is obfuscated config which makes it hard to make changes.


  2. Prevent misconfigurations by understanding the impact of a config change.

  1. Easily understand which config goes where becuase secrets and parameters are well organized. The alternative is obfuscated config which makes it hard to make changes.


  2. Prevent misconfigurations by understanding the impact of a config change.

Benefits

Benefits

  1. Config is organized so you can drill in/out and see only the config you care about but still have access to the big picture.


  2. Onboard new team members faster because the "black art of config" is easy to understand.


  3. Team scale communication is easier because sharing of data and your project structure.

  1. Config is organized so you can drill in/out and see only the config you care about but still have access to the big picture.


  2. Onboard new team members faster because the "black art of config" is easy to understand.


  3. Team scale communication is easier because sharing of data and your project structure.

Examples

Examples

  1. Implement a standardized way to share config patterns across all projects and teams.


  2. Organizing the config makes it easy to understand it. A new team member wants to change a parameter for a specific service. Because the config is obvious and easily understood, making that change without involving others is easy.


  3. For complex, shared configuration that affects multiple components, an organized config allows you to make singular changes that reliably affect multiple components. If the database host changes, every system will get the updated value.

  1. Implement a standardized way to share config patterns across all projects and teams.


  2. Organizing the config makes it easy to understand it. A new team member wants to change a parameter for a specific service. Because the config is obvious and easily understood, making that change without involving others is easy.


  3. For complex, shared configuration that affects multiple components, an organized config allows you to make singular changes that reliably affect multiple components. If the database host changes, every system will get the updated value.