WS-195, WS-76: Notification System now working and sending emails on request submission and completion

Changed workflow temp location from `$(HOME)/workspaces_tmp` (`/root/workspaces_tmp` in the container) to `/tmp/workspaces_tmp`

Daniel Lyons authored 4 years ago and Nathan Hertz committed 4 years ago

Added the ability to compare capability executions by their creation timestamp; made it so encountering exceptions when receiving messages does not block the system

Daniel Lyons authored 4 years ago and Nathan Hertz committed 4 years ago

- Datafetcher runs in container and retrieves data
- Delivery can deliver data to a directory within the container

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

 - Add columns to tables workflow_requests and capability_requests
 - Make the updated_at column auto-update in the database for both
 - Use in the __repr__ method for Python for human-friendliness

Manually verified that the timezone manipulations were correct

 - 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

Updated `testing/utils/conftest.py` with reliable mock data that can be used in tests; added `shared/workspaces` tests

WS-101: figured out how to write pytest tests. test_load_engine works, stubs for other tests created

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

existing executions cannot be deleted (they must be disabled instead,
which will have to be implemented)

Refactored execution management logic out of `CapabilityService` into a new class `ExecutionManager`

`CapabilityService.create_request` instead of duplicating that logic
within the view; changed tests and mocks to go along with the changes

fix CapabilityEngine to actually load the capability execution it's executing and then properly release the engine after completion

Added two new Pyramid views, the first of the capability request views: `view_capability_request` and `create_capability_request`

added views directory that will hold logic for views

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

Daniel Lyons authored 4 years ago and Daniel Lyons committed 4 years ago

Separate architecture from readme in delivery

AKA please don't give me heart failure again

* This feature branch replaces the one in !53, which broke the build.