feat: add platform deployment artifacts

This commit is contained in:
2026-03-25 15:06:14 +00:00
parent 4441dd8afe
commit 7928b5778e
9 changed files with 426 additions and 0 deletions

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

@@ -0,0 +1,41 @@
# Modernization Plan for vetclinic
## Application Type
Java Application
## Selected Modernization Strategy
- **Migration Approach**: containerize-optimize
- **Target Platform**: kubernetes-humanitec
- **Observability**: ENABLED (Prometheus metrics, health checks, tracing)
- **Security Scanning**: ENABLED (Trivy vulnerability scanning)
## Discovery Summary
### Discovery Report
#### Application Overview
The application appears to be a Java-based web application built using the Spring Boot framework. It includes both Maven and Gradle build files, suggesting flexibility in build tool usage. The presence of `spring-petclinic` indicates that this might be a sample or reference application for Spring Boot.
#### Technology Stack
- **Programming Language:** Java
- **Framework:** Spring Boot
- **Build Tools:** Maven (`pom.xml`) and Gradle (`build.gradle`...
## Generated Artifacts
1. **Dockerfile**: Optimized with health checks and metrics endpoints
2. **score.yaml**: Platform-agnostic environment intent optimized for kubernetes-humanitec with Prometheus metrics resources
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: kubernetes-humanitec
score.yaml is the single environment intent. Use Humanitec Platform Orchestrator for deployment.