Files
reno-demo-16/docs/migration-plan.md
demo-bot bf775727e2 feat: modernize application — source, platform artifacts, CI/CD
- chore: ingest source code

112 files from https://github.com/spring-projects/spring-petclinic
- feat: add platform deployment artifacts
- feat: add CI/CD workflow automation
2026-08-05 18:13:54 +00:00

1.6 KiB

Modernization Plan for reno-demo-16

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

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 configurations, suggesting flexibility in build tools. The presence of spring-petclinic indicates it might be a sample or reference application for Spring Boot.

Technology Stack

  • Language: Java
  • Framework: Spring Boot
  • Build Tools: Maven and Gradle
  • Database: H2 (embedded), MySQL, Post...

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.