- Local cluster can now run download workflows
- wf_monitor's timeout functionality now works the way we expect it to

removed EXPOSE cmd in frontend's Dockerfile.dev and added empty dependencies to CI stages that don't need artifacts for efficiency

Added stubbed front-end support for calibration (the button prints to the console when clicked instead of launching a capability normally)

- Capability request status page now grabs all correct information from its request and fills that into the UI
- If the request is complete and the execution has a delivery URL, a download button appears on the page linking to the download area

help

- Two new `npm` packages (not including deps): `eslint` (linter for TypeScript code) and `prettier` (multi-language web-stack code formatter)
- New workspaces component: `capability-request` which is where the work for the page is being done

 - New DestinationTempFile for writing tempfiles into the destination which eventually get added
 - All of the close() methods are now streaming
 - Implemented ChecksumDecorator
 - Implemented FetchFile decorator

- made our volume mounts dynamic with ENV variable
- changed our test deployment trigger with git tags as end-of-sprint-[0-9]+

that clicking the buttons creates corresponding requests and executions

changing default spl to smaller image spl

Charlotte Hausman authored 4 years ago and Nathan Hertz committed 4 years ago

Messaging system is now running on a more robust foundation:
- `kombu` package for AMQP networking
- New Messenger and Router objects
- New message format
- Easy-to-use callback subscribing
- Can now get messages anywhere in the system easily and send replies back easily

 - REST API for Workflows is significantly revamped
 - REST API is now documented with Swagger
 - JSON Arguments to workflows and capabilities are now saved in Postgres properly

- Added PATH_PREFIX variable to build stage to handle dockerfiles at paths other than /services
- removed .unit-test template from .gitlab-ci.yml because it was duplicated

REST API gives out and parse that into the CapabilityRequest object

launches the download capability; moved the capability launching
functionality from the on-click methods to a new method that gets called
by the on click methods

Also removed a few unused imports and added some padding to the html template for the workspaces component

Created page with a button that will send an HTTP request to the capability server; does not currently work

TODO: Make it work with the capability service

Also, added more failfast options to the boot-local scripts