mythical-client
============
.. image:: https://magnum.travis-ci.com/verygoodgroup/mythical-client.svg?token=ykTaJtscxcuMJxYq2Nt5&branch=travis
:target: https://magnum.travis-ci.com/verygoodgroup/mythical-client
test
====
.. code:: bash
$ git clone git@github.com:verygoodgroup/mythical-client.git
$ cd mythical-client
$ git submodule update --init --recursive
$ mkvirtualenv mythical-client
(mythical-client)$ pip install -e .[tests]
(mythical-client)$ export \
MYTHICAL_SUITE_ROOT=https://mythical-test-4w3ebo.vgs.io \
MYTHICAL_SUITE_USERNAME=company \
MYTHICAL_SUITE_PASSWORD=password
(mythical-client)$ py.test suite.py --cov=mythical
suite
=====
If you have many suite targets (e.g. test, local, proxied, etc.) dump them in
``~/.mythical`` like e.g.:
.. code:: bash
$ cat <<EOF >> ~/.mythical
[suite:dev]
http_root=https://vault-all-dev-b6oy83-mythical-http.noxious.io
sftp_host=vault-all-dev-b6oy83-mythical-sftp.noxious.io
sftp_port=8022
username=travis-057e4f1be6c742cc876af9d8cdc74981
password=xxxxxxxxxxxxxxxxxxx
EOF
and target them like:
.. code:: bash
(mythical-client)$ MYTHICAL_SUITE=dev py.test suite.py
...
proxy
=====
To route through a `token proxy <https://github.com/verygood/vault>`_ install the client:
.. code:: bash
(mythical-client)$ pip install vault
setup a target:
.. code:: bash
(mythical-client)$ cat <<EOF >> ~/.mythical
[suite:dev-proxy]
http_root=https://mythical-LoadBala-1RZB12W0TY5A0-1578257076.us-west-2.elb.amazonaws.com
sftp_host=mythical-LoadBala-1RZB12W0TY5A0-1578257076.us-west-2.elb.amazonaws.com
sftp_port=8022
username=vault
password=vaultvault
tokenize=
import vault
token_key = """\
-----BEGIN PUBLIC KEY-----
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDFJEBRUTO6URKuJYboKeSeYYIa
a4AE4zN/bZg/q+F/6y9mODqUC8Ldye6M4a+rSSC8ilVJ7UuLGnVGUztg9VVpBdt5
a1WTpvf4VnyqSkKhQkQ95La7y98FDm8HEI5DZvSlROG39fdyUfTl9PDlEfK9nf40
jQmoXIeRgEF9l2LFiwIDAQAB
-----END PUBLIC KEY-----\
"""
token_version = '0'
tokenize = vault.ephemeral.InlineTokenizer.from_config(
vault.ephemeral.InlineTokenizer.Config(
key=token_key, version=token_version
))
EOF
and test:
.. code:: bash
(mythical-client)$ MYTHICAL_SUITE=dev-proxy py.test suite.py
Metadata
Release files for mythical 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mythical-0.2.0.tar.gz | 10.3 kB | Without provenance | Details for mythical-0.2.0.tar.gz |
Release files / mythical-0.2.0.tar.gz
| Download URL | mythical-0.2.0.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2790813341eaf61e09ccc9284c8ec4bf23d843e9f876ad2c441239aad72d5f49
|
|
BLAKE2b-256 checksum How to use checksums |
3b469dc0b8fc172e07068053111c0bab128436d96178f86d5aa1d48971fbbd2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mythical 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.