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

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

Make the workflow_info and workflow_service singletons the same way their upper-division peers are in the capability service

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

 - 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

This reverts commit 68320db2.

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

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)

and capability request)

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

- 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

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

forgot to add in the previous MR

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

updated coveragerc config files to reflect changes to the shared packages location and modified run-tests.sh

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

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

All enabled tests are now true unit tests with no external dependencies; new `requirements.txt` file in `test/` that installs testing requirements (`pytest`, `pytest-mock`, etc.); and `run-tests.sh` now has an extra step that installs these

Added run-tests.sh script to each service to run our package tester to enable us
to run unit tests from the cmdline and CI
Refactored makefile's make test script to call run-tests.sh in each image