Overview
EBCommander is intended as an interaction layer between Python and EBCommand (https://command.elektrobit.com). It can either be used as a module or directly via Commandline.
Preconditions
The script depends on the following Python packages
- beautifulsoup4
- requests
- pyyaml
Use as module
Import EBCommand.
from ebcommander import EbCommand
Create an instance (this starts the initial data retrieval which may take a while, therefore, it should be considered to run it asynchronously).
commander = EbCommand('your-user', 'your-password')
For more information please have a look at doc.
Use from the Commandline
Direct call
For simple requests (e.g. just to get a glimpse at a specific file) the script can be called with the following arguments
| Argument | Description |
|---|---|
| --json | JSON file to which filtered data shall be written |
| --yaml | YAML file to which filtered data shall be written |
| --filter | File filter pattern |
| --download | Path to which the files shall be downloaded |
Complex calls
For more versatile operations a config file must be provided. It can contain several settings to apply filters on projects, distributions, versions and files, store JSON and YAML files and download the retrieved files. For more information see example-config.yaml
The config is provided by the following arguments
| Argument | Description |
|---|---|
| --config | Path to config for more complex setups |
Regardless, if direct or compex calls, the following arguments must be provided
| Argument | Description |
|---|---|
| --user | EBCommand username |
| --password | EBCommand user password |
Additionally, the following arguments can optionally be provided
| Argument | Description |
|---|---|
| --proxy-http | HTTP proxy (e.g. http://localhost:1234) |
| --proxy-https | HTTPS proxy (e.g. https://localhost:1234) |
1 maintainer
Metadata
1 maintainer
Release files for ebcommander 1.0.1
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 | |
|---|---|---|---|---|
| ebcommander-1.0.1.tar.gz | 11.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ebcommander-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.4 kB
Release files / ebcommander-1.0.1.tar.gz
| Download URL | ebcommander-1.0.1.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e657335c1ef777ad2075f0a12f499c69b02718ee5d53b226ca049e76567f34f
|
|
BLAKE2b-256 checksum How to use checksums |
54ce81d0adf4bcc3beb184c9c63bd856281567289b0a7301dbc3bc9a16c849c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Release files / ebcommander-1.0.1-py3-none-any.whl
| Download URL | ebcommander-1.0.1-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9551076ab0e4d9f5ddd8c528652d99132373906acdeee5178909c99a54edc7d
|
|
BLAKE2b-256 checksum How to use checksums |
b69db00c413d01a96fe692d1cecd067f450812688580f16d361588b2696fff2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Security for ebcommander 1.0.1
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.
