## Host reporting dashboard with Spring Boot: structured data imports

Deploy a reporting dashboard built with Spring Boot on Ample using the bulk import staging pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Spring Boot: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the reporting dashboard-specific behavior as your application code.

### Workflow Steps
1. **Build and start**  
   `./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT. The server must bind 0.0.0.0 on PORT.`

2. **Implement the pattern on PostgreSQL**  
   The fixture's module implements bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Wire object storage**  
   Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.

4. **Deploy**  
   Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.  
   Command: `ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.  
   Command: `ample logs  --kind build`

### Considerations
- **Resource Requirements**:  
   - Compute  
   - PostgreSQL  
   - S3-compatible object storage

- **Limitations**:  
   - Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates and Spring Boot major versions are not verified.  
   - Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Components**:  
  - App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0  
  - Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0

### Next Actions
- **Browse the catalog index**: `GET /v1/catalog`  
- **Search published recipes by intent, stack and constraints**: `POST /v1/catalog/search`  
- **Prepare a side-effect-free deployment plan for an authorized project**: `POST /v1/catalog/plan`  
- **Browse Reporting dashboard**: `GET /v1/catalog/nodes/workload%3Areporting-dashboard`  
- **Browse Spring Boot**: `GET /v1/catalog/nodes/stack%3Aframework-spring-boot`

### Examples
- **Spring Boot pattern fixture**  
   - Description: Multi-pattern Spring Boot app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
   - Source Reference: `tests/deploy-canaries/spring-boot-patterns`

### Evidence Summary
- **Canary Run**: Spring Boot pattern fixture deployed on Ample. Checks passed for bulk-import-staging and configuration-secrets.