41 lines
1.5 KiB
Markdown
41 lines
1.5 KiB
Markdown
# Roadmap & Future Enhancements
|
|
|
|
Tracking pending features and architectural improvements. Extracted from the original `AGENTS.md` (Tâche 6 restructure). Status updated continuously — items move to "Completed Features" section once shipped.
|
|
|
|
## Potential Features
|
|
|
|
- [ ] Database integration
|
|
- [ ] Authentication / Authorization
|
|
- [ ] Rate limiting
|
|
- [ ] Metrics and monitoring
|
|
- [ ] Docker containerization
|
|
- ✅ CI/CD pipeline ([ADR-0016](../adr/0016-ci-cd-pipeline-design.md), [ADR-0017](../adr/0017-trunk-based-development-workflow.md))
|
|
- [ ] Configuration hot reload
|
|
- [ ] Circuit breakers
|
|
|
|
## Architectural Improvements
|
|
|
|
- [ ] Request validation middleware
|
|
- ✅ OpenAPI / Swagger documentation with embedded spec
|
|
- [ ] Enhanced OpenTelemetry instrumentation
|
|
- [ ] Metrics collection and visualization
|
|
- [ ] Health check improvements
|
|
- [ ] Configuration validation enhancements
|
|
|
|
## Completed Features
|
|
|
|
- ✅ Graceful shutdown with readiness endpoint
|
|
- ✅ OpenTelemetry integration with Jaeger support
|
|
- ✅ Configuration management with Viper
|
|
- ✅ Comprehensive logging with Zerolog
|
|
- ✅ Build system with binary output
|
|
- ✅ Complete documentation with commit conventions
|
|
- ✅ Version management with runtime info
|
|
|
|
## How to Propose a New Feature
|
|
|
|
1. Open a Gitea issue describing the use case and acceptance criteria
|
|
2. If the feature implies an architectural decision, draft an ADR (`adr/<NNNN>-<slug>.md`) following the template
|
|
3. Reference the ADR + issue in any PR introducing the feature
|
|
4. Update this roadmap (move from "Potential" to "Completed" when shipped)
|