feat: modernize application — source, platform artifacts, CI/CD

- chore: ingest source code

113 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-11-19 17:45:57 +00:00
parent 0ef56b1165
commit 94c65c6e7e
14 changed files with 876 additions and 722 deletions

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

@@ -0,0 +1,41 @@
# Modernization Plan for demo-hannes-1
## 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 is a Java-based project using the Spring Boot framework. It includes both Maven and Gradle build files, but the presence of `pom.xml` suggests that Maven is the primary build tool. The application appears to be a web application, potentially a Spring PetClinic or a similar project, based on the dependencies and API endpoints.
#### Technology Stack
- **Programming Language**: Java
- **Framework**: Spring Boot
- **Build T...
## 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.