E2E CLI
Stable Release : version - 0.9.30
The E2E Command Line Interface is a unified tool to manage all your E2E services A command line tool developed by E2E Networks Ltd
Getting started
Just Login to your E2E myAccount and get your access tokens. For more on access token refer E2E Tokens Add this to your system and you are all set to go.
Requirements
The e2e-cli package works on Python versions:
3.x and greater
setuptools 45.2.0 or greater
requests 2.22.0 or greater
Notices
Attention! We recommend that all customers regularly monitor the E2E docs website for any important update bulletins related to e2e-cli.
Installation
Installation of the E2E CLI and its dependencies use a range of packaging features provided by pip and setuptools. To ensure smooth installation, it’s recommended to use:
pip: 21.0 or greater requests: 2.22.0 or greater setuptools: 45.2.0 or greater
The safest way to install the E2E CLI is to use pip in a virtualenv: pip install e2e-cli
Configuration
Before using the E2E CLI, you need to configure your E2E credentials/Tokens This can be done by running the following commands to add token, more :
e2e_cli alias add -> To add api key and auth token
e2e_cli alias add_file -> To add api key and auth token via file
Further set default token by using :
e2e_cli alias set -> To set default alias for system
Basic Commands
An E2E CLI command has the following structure:
e2e_cli <command> <subcommand> [options and parameters]
For example, to list buckets, the command would be:
e2e_cli bucket list
To view help/man documentation, use one of the following:
e2e_cli help
To get the version of the E2E CLI:
e2e_cli --version/-v
To get the package info of the E2E CLI:
e2e_cli --info
To turn on debugging :
e2e_cli <command> <subcommand> --debug
To get API arguments info :
e2e_cli <command> <subcommand> --info
Support
For support/help refer E2E CLI docs or visit E2E Networks
Authors and acknowledgment
Aman and Sajal, E2E Networks Ltd.
Project status
Currently undergoing feature upgrades
Release files for e2e-cli 0.9.30
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 |
|---|---|---|---|---|
| e2e_cli-0.9.30.tar.gz | 49.8 kB | Without provenance | Details for e2e_cli-0.9.30.tar.gz |
Release files / e2e_cli-0.9.30.tar.gz
| Download URL | e2e_cli-0.9.30.tar.gz |
|---|---|
| Size | 49.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3465450d78d70d310e3354f21f1aa436fbdc42c68096d66eb7a5da1d0c5eb6ce
|
|
BLAKE2b-256 checksum How to use checksums |
aa225b4d0c9444f6c6e71e85400bf017e8468db795a6ee57d07c811a2052ae31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.1
|
Security for e2e-cli 0.9.30
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.
