### Host inventory manager with Spring Boot: CSV imports

#### Summary
Deploy an inventory manager 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 inventory manager-specific behavior as your application code.

#### Prerequisites
- A Spring Boot project that builds and starts with the documented commands (./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).
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
- An Ample account token with servers:write, databases:read, buckets:read.

#### 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 <app-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`

#### Success Checks
- App responds on its public URL.
  - Kind: http_get  
  - Path: /  
  - Expect: ample canary spring boot patterns  
- Bulk-import-staging self-test.
  - Kind: http_get  
  - Path: /p/bulk-import-staging  
  - Expect: imported=2 rejected=1 restart=ok
  
#### 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.
- The inventory manager itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not verified.

#### Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Authoritative: true
- Basis: size prices from pricing.toml at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- Components:
  - Name: app server  
    Size: s-1vcpu-1gb  
    Quantity: 1.0  
    Monthly Amount: 5.0  
  - Name: managed PostgreSQL database  
    Size: s-1vcpu-1gb  
    Quantity: 1.0  
    Monthly Amount: 5.0  
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

#### Evidence Summary
- Kind: canary_run  
  Summary: Spring Boot pattern fixture deployed on Ample.  
  Observed At: 2026-09-21T02:34:39Z  
  Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)  
  Expires At: 2027-03-20T02:34:39Z

- Kind: canary_run  
  Summary: The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.  
  Observed At: 2026-09-20T22:49:19Z  
  Implementation Revision: af6f45adea26-dirty (CLI af6f45a)  
  Expires At: 2027-03-19T22:49:19Z

#### Next Actions
- Browse the catalog index: /v1/catalog
- Search published recipes by intent, stack and constraints: /v1/catalog/search (POST)
- Prepare a side-effect-free deployment plan for an authorized project: /v1/catalog/plan (POST)
- Read the existing agent authentication setup: /mcp/setup
- Browse Inventory manager: /v1/catalog/nodes/workload%3Ainventory-manager
- Browse Spring Boot: /v1/catalog/nodes/stack%3Aframework-spring-boot
- Browse Bulk import staging: /v1/catalog/nodes/pattern%3Abulk-import-staging
- Browse Deploy web app: /v1/catalog/nodes/intent%3Adeploy-web-app