This document discusses different approaches to configuration management and their issues. It proposes building an in-house configuration management solution to avoid costs of specialized services, reduce developer workload, and provide an easy workflow for operations teams. Key requirements for the in-house solution include automatic validations, reviews and approvals, versioning, change logging, no downtime during updates, and supporting multiple environments.

2. Why?
- Config management is a rather common problem
- There are many solutions with various complexity / suitability
- In-house made stuff
- Specialized services
- But they have issues...

3. Custom Solutions
- Storing in databases / file storages
- HTTP endpoints for configuration
- Bespoke UI

4. Problems with Custom Solutions
- Extra development
- Maintenance and support
- Users education
- Hard to implement all requirements

5. Specialized Services / Products
- Frameworks (Spring Cloud Config)
- Cloud Solutions (AWS Config / Azure App Configuration)
- Configuration Management Tools

6. Problems
- Might be expensive
- Might not fit your stack
- Might have limitations (eg. rate / instance limits for cloud
services)
- Learning curve

7. What
- We want services to be configured
- Configuration changes should not involve dev teams
- Less work for devs (use native framework tools for
configuration)
- Easy workflow for operations
- No extra costs for business (inhouse development, user
education etc.)

8. Requirements
- Automatic validations
- Reviews and approvals
- Versioning (view history, revert to previous versions etc.)
- Change log
- No downtime during updates
- Fast propagation
- Support different environments / sites etc.

9. Start the Action...

10. Next steps
- Chatbots
- Sheets file generation
- Custom workflows

11. Thanks!
@skalinets