# Host help desk with ASP.NET Core: CSV imports

Deploy a help desk built with ASP.NET Core 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 ASP.NET Core: 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 help desk-specific behavior as your application code.

## Representative Queries
- Host help desk with ASP.NET Core: CSV imports
- Where can I host Help desk built with ASP.NET Core?
- I need a domain CSV format, row validation, deduplication and an import recovery path.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## Infrastructure Requirements
### Compute
- **Label**: 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.

### Postgres
- **Label**: 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.

### S3-compatible object storage
- **Label**: 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.

## Workflow Steps
1. **Build and start**  
dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to 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

## Examples
- **Title**: ASP.NET Core pattern fixture  
  **Description**: Multi-pattern ASP.NET Core app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  **Source Reference**: tests/deploy-canaries/asp-net-core-patterns

## Success Checks
- **HTTP GET** on `/`  
  **Expect**: ample canary asp net core patterns
- **HTTP GET** on `/p/bulk-import-staging`  
  **Expect**: imported=2 rejected=1 restart=ok

## Limitations
- Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture; other sizes, templates and ASP.NET Core major versions are not verified.
- The help desk 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
- **Components**:
  - **App Server**: 1.0 x s-1vcpu-1gb at $5.0
  - **Managed PostgreSQL Database**: 1.0 x s-1vcpu-1gb at $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**: ASP.NET Core pattern fixture deployed on Ample with checks passed for bulk-import-staging and configuration-secrets.
  **Observed At**: 2026-09-21T01:15:54Z
- **Kind**: canary_run  
  **Summary**: The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.
  **Observed At**: 2026-09-20T23:34:47Z

## Last Verified At
- 2026-09-21T01:15:54Z

## Next Actions
- **Action**: Browse the catalog index  
  **Method**: GET  
  **Relative Path**: /v1/catalog
- **Action**: Search published recipes by intent, stack and constraints  
  **Method**: POST  
  **Relative Path**: /v1/catalog/search  
  **Body**: {"limit":5,"query":"Host help desk with ASP.NET Core: CSV imports"}
- **Action**: Prepare a side-effect-free deployment plan for an authorized project  
  **Method**: POST  
  **Relative Path**: /v1/catalog/plan  
  **Body**: {"inputs":{},"projectId":"","recipeId":"page:recipes:help-desk:asp-net-core:csv-imports","recipeRevision":"r1"}
- **Action**: Read the existing agent authentication setup  
  **Method**: GET  
  **Relative Path**: /mcp/setup
- **Action**: Browse Help desk  
  **Method**: GET  
  **Relative Path**: /v1/catalog/nodes/workload%3Ahelp-desk
- **Action**: Browse ASP.NET Core  
  **Method**: GET  
  **Relative Path**: /v1/catalog/nodes/stack%3Aframework-asp-net-core
- **Action**: Browse Bulk import staging  
  **Method**: GET  
  **Relative Path**: /v1/catalog/nodes/pattern%3Abulk-import-staging
- **Action**: Browse Deploy web app  
  **Method**: GET  
  **Relative Path**: /v1/catalog/nodes/intent%3Adeploy-web-app