Create Azure migration plan for PhotoAlbum Java application

[Copilot]

Generated comprehensive modernization plan to migrate PhotoAlbum Java app from on-premises Oracle/Docker stack to Azure managed services.

Plan Structure

• Branch: 001-migrate-photoalbum-to-azure
• Location: .github/modernization/001-migrate-photoalbum-to-azure/plan.md
• Tasks: 7 sequential migration tasks with validated solution IDs

Migration Scope

Current: Java 8 + Spring Boot 2.7.18 + Oracle Database 21c XE
Target: Java 17 + Spring Boot 3.x + Azure Database for PostgreSQL + Azure Container Apps

Task Breakdown

1. Java Upgrade: Spring Boot → 3.x (includes JDK 8→17, Jakarta EE migration)
2. Database: Oracle → PostgreSQL with BLOB→BYTEA conversion
3. Secrets: Plaintext credentials → Azure Key Vault
4. Auth: Database connection → Managed Identity (passwordless)
5. Sessions: Local in-memory → Azure Cache for Redis
6. Logging: File-based → Console output for Azure Monitor
7. Deploy: Generate Bicep templates and deploy to Azure Container Apps

Architecture Diagrams

Includes Mermaid diagrams showing current Docker Compose architecture and target Azure services architecture with managed identities and cloud-native integrations.

Execution

Plan ready for /appmod-kit.run-plan execution. All solution IDs validated against appmod knowledge base.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>plan for the migration</issue_title>
<issue_description> run .github\prompts\appmod-kit.create-plan.prompt.md to migrate this app to azure</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes plan for the migration #8

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.