feat: modernize application — source, platform artifacts, CI/CD
Some checks failed
Build and Publish TechDocs / build-and-publish (push) Successful in 59s
Build and Push to ACR / Build and Push (push) Successful in 5m2s
SonarQube Analysis / Build, Test & Analyse (pull_request) Failing after 30s
Integration Test / Unit Tests + Container Smoke (workflow_dispatch) Some checks failed

- chore: ingest source code

108 files from https://github.com/spring-projects/spring-petclinic
- feat: add platform deployment artifacts
- feat: add CI/CD workflow automation
This commit is contained in:
2026-05-18 21:14:53 +00:00
parent a4d8956731
commit 69b0b0b729
14 changed files with 874 additions and 462 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": "demo-cp4-1"}
```
### Root
```
GET /
```
**Response:**
```json
{"service": "demo-cp4-1", "description": "Modernized demo-cp4-1 service", "version": "1.0.0"}
```

15
docs/architecture.md Normal file
View File

@@ -0,0 +1,15 @@
# Architecture
## Service Design
demo-cp4-1 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 @@
# demo-cp4-1
Modernized demo-cp4-1 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/demo-cp4-1.git
cd demo-cp4-1
```
## Monitoring
- **Metrics**: Prometheus metrics at `/metrics`
- **Health**: `/health`
- **Grafana**: [View Dashboard](https://grafana.kyndemo.live/d/app-demo-cp4-1)
## Support
Contact the Platform Engineering team.

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

@@ -0,0 +1,47 @@
# Modernization Plan for demo-cp4-1
## Application Type
Java Application
## Selected Modernization Strategy
- **Migration Approach**: containerize-optimize
- **Target Platform**: humanitec-v2
- **Observability**: ENABLED (Prometheus metrics, health checks, tracing)
- **Security Scanning**: ENABLED (Trivy vulnerability scanning)
## Discovery Summary
### Discovery Report
#### Application Overview
- **Path**: `/tmp/modernize_50dcmnne`
- **Type**: Java-based application using Spring Boot framework.
- **Build Tools**: Maven and Gradle are both configured, indicating flexibility in build management.
#### Technology Stack
- **Framework**: Spring Boot
- **Primary Features**:
- Web MVC for RESTful APIs and web pages.
- Data JPA for database interactions.
- Thymeleaf for server-side rendering.
- Actuator for monitoring and management.
- ...
## 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: humanitec-v2
score.yaml optimized for Azure Container Apps with managed scaling and Azure-specific configuration.