enumeray artifact upload

Hash a local file, save a retryable operation and upload it as a verified artifact.

Use when: You need an independent reusable upload; analysis file bindings handle ordinary execution inputs automatically.

Role and prerequisites: Authenticated account with uploads:create, uploads:read and uploads:complete; standalone upload requires no model access. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray artifact upload ./dataset.csv --name dataset.csv --media-type text/csv --state upload-state.json

Upload metadata defaults to {}. For private structured metadata, pass --metadata metadata.json. Do not submit the upload state file as a model input.

Inputs and options

Input	Meaning and use
<FILE>	Existing local source file. Keep its bytes/path unchanged until completion or resume; the saved state verifies the expected digest.
--name <NAME>	Artifact file name for metadata, such as dataset.csv. The source path is supplied separately.
--media-type <MEDIA_TYPE>	Media type describing uploaded bytes, such as text/csv or application/octet-stream. It does not convert or validate the scientific contents.
--metadata <METADATA>	Optional JSON object with user metadata for the upload; defaults to {}. Do not put credentials in metadata.
--state <STATE>	New private upload-operation file, created before reserving or transferring bytes. It retains the original source checksum, upload reservation and retry identity. Keep the same API/account and unchanged source bytes; reuse this file with artifact resume after interruption.

Every command also accepts the profile, API, JSON and timeout options.

Result and next step

Saves private retry state before contacting the API, then reserves, transfers and completes the upload. The final artifact identity is usable by run inputs; an upload reservation alone is not.

On uncertain outcome, run artifact resume with the same state. Reuse verified completion metadata in analysis inputs, or retain it for independent data operations.

Exact syntax, defaults and accepted values

Prepare a verified upload and save retry state before contacting the API

Usage: enumeray artifact upload [OPTIONS] --name <NAME> --media-type <MEDIA_TYPE> --state <STATE> <FILE>

Arguments:
  <FILE>  Existing local source file; retain its path and exact bytes until upload completes

Options:
      --api <API>                User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --name <NAME>              Artifact filename stored as metadata, for example dataset.csv; independent of the local source path
      --media-type <MEDIA_TYPE>  Media type of uploaded bytes, such as text/csv; does not convert their contents
      --profile <PROFILE>        Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>          Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --metadata <METADATA>      Optional scientific metadata JSON object file; defaults to {}
      --json                     Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --state <STATE>            New private upload-state JSON file, saved before API contact; use artifact resume after interruption
      --timeout <TIMEOUT>        User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help                     Print help