feat: modernize application — source, platform artifacts, CI/CD (#3)
All checks were successful
Build and Push to ACR / Build and Push (push) Has been skipped
Build and Publish TechDocs / build-and-publish (push) Successful in 1m37s

This commit was merged in pull request #3.
This commit is contained in:
2026-10-13 16:22:33 +00:00
parent e3952b7120
commit a4d57bb1a6
12 changed files with 728 additions and 368 deletions

25
docs/api.md Normal file
View File

@@ -0,0 +1,25 @@
# API Reference
## Endpoints
### Health Check
```
GET /health
```
**Response:**
```json
{"status": "UP", "service": "vehicle-telematics"}
```
### Root
```
GET /
```
**Response:**
```json
{"service": "vehicle-telematics", "description": "Modernized vehicle-telematics service", "version": "1.0.0"}
```

15
docs/architecture.md Normal file
View File

@@ -0,0 +1,15 @@
# Architecture
## Service Design
vehicle-telematics is a microservice following cloud-native patterns.
## Technology Stack
- **Runtime**: Java Spring Boot
- **Deployment**: Humanitec Platform Orchestrator
- **CI/CD**: Gitea Actions → ACR → Humanitec
## Dependencies
See `score.yaml` for external resource dependencies.

32
docs/index.md Normal file
View File

@@ -0,0 +1,32 @@
# vehicle-telematics
Modernized vehicle-telematics service
## Overview
This service is built with **Java Spring Boot** and follows the Golden Path architecture patterns.
### Key Features
- 🚀 Production-ready configuration
- 📊 Prometheus metrics exposed
- 🏥 Health check endpoints
- 🔒 Security scanning in CI/CD
- 📦 Containerized deployment
## Quick Start
```bash
git clone https://gitea.kyndemo.live/kyndryl-demos/vehicle-telematics.git
cd vehicle-telematics
```
## Monitoring
- **Metrics**: Prometheus metrics at `/metrics`
- **Health**: `/health`
- **Grafana**: [View Dashboard](https://grafana.kyndemo.live/d/app-vehicle-telematics)
## Support
Contact the Platform Engineering team.

45
docs/migration-plan.md Normal file
View File

@@ -0,0 +1,45 @@
# Modernization Plan for vehicle-telematics
## Application Type
Java Application
## Selected Modernization Strategy
- **Migration Approach**: containerize-optimize
- **Target Platform**: orchestrator
- **Observability**: ENABLED (Prometheus metrics, health checks, tracing)
- **Security Scanning**: ENABLED (Trivy vulnerability scanning)
## Discovery Summary
### Application Discovery Report
#### Application Overview
The application located at `/tmp/modernize_kri87tky` appears to be a **Java Spring Boot** application. This is evident from the presence of files such as `pom.xml`, `build.gradle`, and Spring Boot-specific dependencies.
---
### Technology Stack
- **Programming Language**: Java
- **Framework**: Spring Boot
- **Build Tools**: Maven and Gradle (both configurations are present)
- **Database**: H2 (in-memory), MySQL, PostgreSQL
- **Fronten...
## Generated Artifacts
1. **Dockerfile**: Optimized with health checks and metrics endpoints
2. **score.yaml**: Platform intent with service ports and DNS resource
3. **CI Workflow**: Automated build/push to ACR with Trivy security scanning
## Next Steps
1. Review and customize generated artifacts
2. Test container build and run
3. Deploy to development environment using score.yaml
4. Validate application functionality
5. Promote to staging/production via Humanitec
## Migration Strategy Details
### Containerize Optimize
Add cloud-native patterns: health checks, metrics, optimized base images.
### Platform: orchestrator
score.yaml optimized for Azure Container Apps with managed scaling and Azure-specific configuration.