aquasec-cli
Aqua Security CLI
Installation
>>> python -m pip install aquasec-cli
Usage
Help Menu of all Groups:
>>> aquasec-cli --help
Usage: aquasec-cli [OPTIONS] COMMAND [ARGS]...
AquaSec CLI tool to manage AquaSec Tenant
Options:
--help Show this message and exit.
Commands:
delete Deletes created API Auth
init Initializes API Auth
reports Generate CIS Bench Reports
>>> aquasec-cli init --help
Usage: aquasec-cli init [OPTIONS]
Initializes API Authentication token used to run commands; required to
generate before a command can be executed
Options:
--csp_roles TEXT Creates Aquasec auth token
--endpoints TEXT Endpoint Call Allowed
--help Show this message and exit.
>>> aquasec-cli reports --help
Usage: aquasec-cli reports [OPTIONS]
Generate CIS Bench Reports
Used to generate CIS Bench Reports in different formats
Options:
-r, --report_type [cis|kube_bench|linux|openshift|disa_stig|all]
Report type to genorate
-c, --cluster_name TEXT Supply Cluster name
-l, --report_location TEXT Directory to write out report to; please
ensure proper formatting given the system
you are on [required]
--report_format [list|flat_list|raw]
Report Format
--help Show this message and exit.
>>> aquasec-cli delete --help
Usage: aquasec-cli delete [OPTIONS]
Deletes created API Auth
Options:
--yes
--help Show this message and exit.
NOTE: Each subcommand has a help menu to assist with the calls being made. This project relies on the yaml or localized configurations being help as they are not passed in the commands as of this release.
Create API Auth Token:
>>> aquasec-cli init --csp_roles="Auditor" --csp_roles="Admin" --endpoints="Any"
Initializing API
INFO : Created WorkloadAuth Token for URL https://1234abcff1.cloud.aquasec.com
Run Report:
aquasec-cli reports --report_type kube_bench --report_location /var/tmp --report_format list
Report completed Saving
Report written out to /var/tmp/aquasec_report_type_kube_bench_20230424T153825.json
Delete API Auth:
>>> aquasec-cli delete
Are you sure you want to delete the auth api token? [y/N]: y
Deleted Auth
Release Info
v0.0.6
- Added error handling
- Added ability to generate different reports
- Updated requirements to new aquasec-api
v0.0.5
- Updated Readme and changed type from RST to MD
- Reverted snyk workflow file
v0.0.4
- fixed issue with broken aquasec-api v0.0.3
v0.0.3
- Fixed installation and dependencies
- locked down dependencies
- added toml and setup.cfg to support furture installations
v0.0.2
- Bug fix with requirements
Version
| Version | Build | Changes |
|---|---|---|
| 0.0.2 | a1 | issues with dataclasses getting installed under normal condition |
| 0.0.2 | final | tested in pytest and seems to now accept the dataclass |
| 0.0.3 | a1 | issues with dataclasses and now yaml getting installed under normal condition |
| 0.0.3 | a3 | migrating to toml and setup.cfg |
| 0.0.3 | a4 | cleaned up utils and updated snyk to confirm pass locally; added to git ignore |
| 0.0.3 | a5 | setup.cfg issues wiht pip |
| 0.0.3 | final | found issue with toml and other dependencies |
| 0.0.4 | final | fixed issue with aquaapi dependency |
| 0.0.5 | a1 | fixed readme to point to md file; adjusting snyk |
| 0.0.5 | final | tested and released |
| 0.0.6 | a1 | removed README.rst updated snyk |
| 0.0.6 | a2 | make delete more efficent added adjustments to report |
Warnings
Use at your own risk!!!
Security Policy
Supported Versions
Use this section to tell people about which versions of your project are currently being supported with security updates.
| Version | Supported |
|---|---|
| 0.0.x | ✓ |
Reporting a Vulnerability
Use this section to tell people how to report a vulnerability.
Tell them where to go, how often they can expect to get an update on a reported vulnerability, what to expect if the vulnerability is accepted or declined, etc.
Metadata
Release files for aquasec-cli 0.0.6
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 |
|---|---|---|---|---|
| aquasec-cli-0.0.6.tar.gz | 44.7 kB | Without provenance | Details for aquasec-cli-0.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aquasec_cli-0.0.6-py3-none-any.whl | Python 3 | none | any | Details for aquasec_cli-0.0.6-py3-none-any.whl |
Total release size: 76.5 kB
Release files / aquasec-cli-0.0.6.tar.gz
| Download URL | aquasec-cli-0.0.6.tar.gz |
|---|---|
| Size | 44.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ec047cf2e0860fb99373e567259ef267deb8ea6ac2c443883899753074d8034
|
|
BLAKE2b-256 checksum How to use checksums |
13c995fe5c29d806e6bb6f42c4d6c0bcc770f463990ec437db9b1ac0de2c7b8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.9
|
Release files / aquasec_cli-0.0.6-py3-none-any.whl
| Download URL | aquasec_cli-0.0.6-py3-none-any.whl |
|---|---|
| Size | 31.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f5c62f9201bd357418179081c423babbf680cb53141941217aa8ff1646f3b86
|
|
BLAKE2b-256 checksum How to use checksums |
1ab900d5529749693804a73fa581d008ddd99cc2d0113af29d12add061eef6f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.9
|
Security for aquasec-cli 0.0.6
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.