Skip to main content

Commandline Utilities for the Legion Alerting and Monitoring System

Project description

Legion CLI

Commandline Utilities for the Legion Alerting and Monitoring System

Setup & Usage

Installation

TODO

Configuration

TODO

Usage

The key reference for using legion-cli is:

legion-cli --help

Development

Standards

  • Be excellent to each other
  • Code coverage must be at 100% for all new code, or a good reason must be provided for why a given bit of code is not covered.
    • Example of an acceptable reason: "There is a bug in the code coverage tool and it says its missing this, but its not".
    • Example of unacceptable reason: "This is just exception handling, its too annoying to cover it".
  • The code must pass the following analytics tools. Similar exceptions are allowable as in rule 2.
    • pylint --disable=C0111,W1203,R0903 --max-line-length=100 ...
    • flake8 --max-line-length=100 ...
    • mypy --ignore-missing-imports --follow-imports=skip --strict-optional ...
  • All incoming information from users, clients, and configurations should be validated.
  • All internal arguments passing should be typechecked whenever possible with typeguard.typechecked

Development Setup

Using poetry install from inside the repo directory:

poetry install

This will set up a virtualenv which you can always activate with either poetry shell or run specific commands with poetry run. All instructions below that are meant to be run in the virtualenv will be prefaced with (legion-cli)$

IDE Setup

Sublime Text 3

curl -sSL https://gitlab.com/-/snippets/2066312/raw/master/poetry.sublime-project.py | poetry run python

Development

Testing

All testing should be done with pytest which is installed with the dev requirements.

To run all the unit tests, execute the following from the repo directory:

(legion-cli)$  pytest

This should produce a coverage report in /path/to/dewey-api/htmlcov/

While developing, you can use watchexec to monitor the file system for changes and re-run the tests:

(legion-cli)$ watchexec -r -e py,yaml pytest

To run a specific test file:

(legion-cli)$ pytest tests/unit/test_cli.py

To run a specific test:

(legion-cli)$ pytest tests/unit/test_cli.py::test_cli_basics

For more information on testing, see the pytest.ini file as well as the documentation.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

legion-cli-0.1.2.tar.gz (16.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

legion_cli-0.1.2-py3-none-any.whl (16.8 kB view details)

Uploaded Python 3

File details

Details for the file legion-cli-0.1.2.tar.gz.

File metadata

  • Download URL: legion-cli-0.1.2.tar.gz
  • Upload date:
  • Size: 16.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.1.6 CPython/3.8.10 Linux/5.4.0-77-generic

File hashes

Hashes for legion-cli-0.1.2.tar.gz
Algorithm Hash digest
SHA256 d8831e5e7e4d2d92f671e4ceeaf310a578d2114cdfb65cfefb434773f874deba
MD5 acb1fb359a72296d69bf4824e28855c3
BLAKE2b-256 675db44bd1565b737f91fb0196f530d82ff92e70c2704dcd2cf37fe333a15276

See more details on using hashes here.

File details

Details for the file legion_cli-0.1.2-py3-none-any.whl.

File metadata

  • Download URL: legion_cli-0.1.2-py3-none-any.whl
  • Upload date:
  • Size: 16.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.1.6 CPython/3.8.10 Linux/5.4.0-77-generic

File hashes

Hashes for legion_cli-0.1.2-py3-none-any.whl
Algorithm Hash digest
SHA256 1ead2a4fa4e5a4812c5560ddf6a21fc0c62ed822a02a5aa2a8b3a15eeed36ef3
MD5 de4be2f88066e20156260d423b3f49a7
BLAKE2b-256 2efe2d8a61efc774ab58ffdccfa333d5d906cf1be829f945e6eda13b8c99bbca

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page