All notable changes to this project will be documented in this file.
This project adheres to Semantic Versioning.
Important
Major version zero (0.y.z) is for initial development. During initial development phase, expect breaking API and YAML schema changes during minor updates. Patch updates are guaranteed to be backward compatible during this phase.]
- Added optional
tagsarray to execution payload. Tags are stored with the job record and can be used to filter jobs when querying/jobs.
- Job responses now includes the
tagsfield.
- The
imageblock now carries adigestSourcefield saying how the digest was determined.
- New
SEPEX_DOCKER_NETWORKenvironment variable (default:sepex_net) to set the docker network that launched job containers are attached to. Set it tohostto run them with host networking, which is required on EC2 for instance profile credential access. - AWS credentials (S3 and Batch) are now resolved through the default AWS credential chain rather than read directly from
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. Deployments that set those variables are unaffected, deployments without them can authenticate with an ECS/EC2 instance role, andAWS_SESSION_TOKENis now honored for temporary credentials. MinIO continues to use its ownMINIO_*keys. - Optional new IAM permission
ecs:DescribeTasksis added. It lets AWS Batch jobs record the digest ECS actually pulled. If not provided, jobs using a moving tag fall back to asking the registry and recordtag-lookup. - Processes are now warned about at startup when their references are not pinned, meaning an
aws-batchjob definition without a revision, or an image that is a moving tag rather thanrepository@sha256:.... These are advisory only and do not stop a process from loading.
- AWS Batch log stream lookup read the region from
AWS_DEFAULT_REGION, which the API never defines, leaving the request without a region. All AWS calls now resolve the region fromAWS_REGION. - The erroneous Docker Hub digest lookup was removed and will be implemented later.
0.2.2 - 2025-2-28
- Execution mode now determined per OGC API - Processes Requirements 25/26: honors
Prefer: respond-asyncheader when process supports both modes, defaults to sync otherwise - Returns
Preference-Appliedresponse header when async preference is honored
- New endpoint to view resource utilization for local jobs (docker, subprocess) and queue status
- Added
recoveryNoticeobject to metadata format
- Added restart recovery for docker, subprocess, and AWS Batch jobs, including status reconciliation and log handling.
- Introduced
lostjob status and surfaced it in UI status indicators (job list, job logs, status table). - Recovered jobs annotate metadata with a recovery notice and write best-effort metadata when some fields are missing.
- Resource pool can force-reserve resources for already-running recovered docker jobs.
- New
MAX_LOCAL_CPUSandMAX_LOCAL_MEMORYenvironment variables (or--max-local-cpusand--max-local-memoryCLI flags) to set resource limits for local job scheduling - Process definitions are validated against these limits at startup and when adding/updating processes via API
- Processes without explicit resource requirements use default values
- Added sequence diagram for local scheduler
- Added Recovery section to DEV_GUIDE
0.2.1 - 2025-12-03
- Version information is added in landing page.
- Repository URL is now configurable via
REPO_URLenvironment variable. This URL is used for version links and metadata context references.
- Changelog updated to new format
0.2.0 - 2025-12-02
- In response body
container_logskey is replaced byprocess_logs
- Request payload schema has changed (See Process YAML Schema changes below)
commandis now a first class object and moved outside ofcontainerconfigobject is addedmaxResourcesandenvVarsare moved underconfigobjectimagemoved underhostcontainerobject removedhost.typevalid options are changed fromlocal|aws-batchtodocker|aws-batch|subprocess
subprocesstype processes now can be executed through API. They must be registered like other processes and will be called using OS subprocess calls.
- A
CHANGELOG.mdfile is added in the repo. - Process templates are provided for all three host types in
./process_templatesfolder - Windows setup instructions are added in
README.md
0.1.0 - 2023-07-07
- Initial release with core API endpoints for process and job management