| docs | |
|---|---|
| tests |    |
| version status | 
|
AWS Lambda to check code signatures to verify both presence and "signed by Mozilla" status.
There are three deployment scenarios for fx-sig_verify:
As an AWS Lambda function - see :ref:`Lambda Installation` for the details.
As a set of command line tools to facilitate usage and operation of the Lambda function:
pip install https://github.com/mozilla-services/fx-sig-verify
See :ref:usage for more details on command line tools
In development mode (see below).
https://fx-sig-verify.readthedocs.io/
At present, fx-sig-verify requires out-of-date (unsupported) software, so
development via Docker is recommended. Be sure Docker is installed on your
development machine.
Typical development setup, using a local virtual environment:
git clone https://github.com/mozilla-services/fx-sig-verify cd fx-sig-verify make
To start a docker instance, with the working directory available in
/root/src:
make docker-shell
NOTE: You'll be running in /usr/src/app, which has a copy of the working
tree. That directory is not persisted. If you need to save modification, be sure
to copy them to /root/src/ before exiting the shell.
NOTE: If you choose to run tests on your development machine, you may need
to install extra packages on your system for M2Crypto & OpenSSL to
compile cleanly.
The local test runner is pytest, with all local tests in the tests/
subdirectory. To run just the tests:
make docker-test
To run the full CI suite on your development machine use:
tox tests
Note, to combine the coverage data from all the tox environments run:
| Windows | set PYTEST_ADDOPTS=--cov-append tox |
|---|---|
| Other | PYTEST_ADDOPTS=--cov-append tox |
Testing on AWS requires an AWS account. Refer to :ref:`Lambda Installation` for details.