Host approval workflow with Quarkus: CSV imports

Summary

Deploy an approval workflow built with Quarkus 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 Quarkus: 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 approval workflow-specific behavior as your application code.

Representative Queries

• Host approval workflow with Quarkus: CSV imports
• Where can I host Approval workflow built with Quarkus?
• I need a domain CSV format, row validation, deduplication and an import recovery path.

Prerequisites

• A Quarkus project that builds and starts with the documented commands (./mvnw -q -DskipTests package producing one uber-jar (quarkus.package.jar.type=uber-jar), then java -jar on the jvm-21 template (Temurin JDK 21) with quarkus.http.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

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

1. Compute

   • Status: verified
   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. Postgres

   • Status: verified
   • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

3. S3-compatible object storage

   • Status: verified
   • Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Tested Configuration

• Template: jvm-21
• Runtime: java
• Size: s-1vcpu-2gb
• Build: ./mvnw -q -DskipTests package
• Start: java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

Workflow Steps

1. Build and start

   • Body: ./mvnw -q -DskipTests package producing one uber-jar (quarkus.package.jar.type=uber-jar), then java -jar on the jvm-21 template (Temurin JDK 21) with quarkus.http.port read from PORT. The server must bind 0.0.0.0 on PORT.

2. Implement the pattern on PostgreSQL

   • Body: 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

   • Body: 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

   • Body: 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

   • Body: 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

1. App responds on its public URL:

   • Kind: http_get
   • Path: /
   • Expect: ample canary quarkus patterns

2. 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 Quarkus major versions are not verified.
• The approval workflow 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
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

Components

1. App server

   • Size: s-1vcpu-1gb
   • Quantity: 1.0
   • Monthly Amount: 5.0

2. 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

1. Kind: canary_run

   • Summary: Quarkus pattern fixture deployed on Ample (./mvnw -q -DskipTests package producing one uber-jar (quarkus.package.jar.type=uber-jar), then java -jar on the jvm-21 template (Temurin JDK 21) with quarkus.http.port read from PORT); checks passed for bulk-import-staging and configuration-secrets. Pattern proof: 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).
   • Observed At: 2026-09-21T00:35:31Z
   • Implementation Revision: c6c81daa9272c95c5ce381005ba7347a341e578f-dirty (CLI 0.1.21)
   • Expires At: 2027-03-20T00:35:31Z
   • Scope:
     • Checks: [/p/bulk-import-staging]
     • Pattern: pattern:bulk-import-staging
     • Template: jvm-21

2. Kind: canary_run

   • Summary: The same Quarkus app deployed with a --release-command migration; the marker it created was readable after activation.
   • Observed At: 2026-09-21T00:35:31Z
   • Implementation Revision: c6c81daa9272c95c5ce381005ba7347a341e578f-dirty (CLI 0.1.21)
   • Expires At: 2027-03-20T00:35:31Z
   • Scope:
     • Pattern: pattern:bulk-import-staging

Last Verified At

2026-09-21T00:35:31Z

Known Issues

• Region availability is unknown until a verified region fact is recorded.
• Compliance attestations are unknown; none are claimed.

Formats

• HTML
• Markdown
• JSON

Next Actions

1. Browse the catalog index

   • Action ID: browse-catalog
   • Method: GET
   • Relative Path: /v1/catalog

2. Search published recipes by intent, stack and constraints

   • Action ID: search-recipes
   • Method: POST
   • Relative Path: /v1/catalog/search
   • Parameters:
     • Body: {"limit":5,"query":"Host approval workflow with Quarkus: CSV imports"}

3. Prepare a side-effect-free deployment plan for an authorized project

   • Action ID: plan:page:recipes:approval-workflow:quarkus:csv-imports
   • Method: POST
   • Relative Path: /v1/catalog/plan
   • Parameters:
     • Body: {"inputs":{},"projectId":"","recipeId":"page:recipes:approval-workflow:quarkus:csv-imports","recipeRevision":"r1"}

4. Read the existing agent authentication setup

   • Action ID: auth-setup
   • Method: GET
   • Relative Path: /mcp/setup

5. Browse Approval workflow

   • Action ID: browse:workload:approval-workflow
   • Method: GET
   • Relative Path: /v1/catalog/nodes/workload%3Aapproval-workflow

6. Browse Quarkus

   • Action ID: browse:stack:framework-quarkus
   • Method: GET
   • Relative Path: /v1/catalog/nodes/stack%3Aframework-quarkus

7. Browse Bulk import staging

   • Action ID: browse:pattern:bulk-import-staging
   • Method: GET
   • Relative Path: /v1/catalog/nodes/pattern%3Abulk-import-staging

8. Browse Deploy web app

   • Action ID: browse:intent:deploy-web-app
   • Method: GET
   • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app