AxoSyslog CFG Helper
This tool makes configuring AxoSyslog a bit easier by listing the options of each available driver.
The options are generated from AxoSyslog v4.28.0.
Quickstart
Install with pipx
pipx install axosyslog-cfg-helper
Or pull the container image
docker pull ghcr.io/alltilla/axosyslog-cfg-helper
List the contexts
axosyslog-cfg-helper
List the drivers in a context
axosyslog-cfg-helper --context parser
List the options of a driver
axosyslog-cfg-helper --context parser --driver csv-parser
Example
Development
The tool is still in development, but most of the drivers are supported.
Missing features are:
- Proper
rewritesupport. - Proper
filtersupport. - Drivers defined in
SCLs. - Drivers defined with confgen.
Any contribution is welcome :)
Local setup
The project uses poetry as a dependency management system.
Building of the option database needs the neologism pip package, which gets installed by poetry, however it has another dependency, which is bison. Make sure to install bison (at least 3.7.6) on you system if you wan't to develop locally. make bison can help with that.
The Makefile consists of some useful commands:
make venvprepares the venv.make bisondownloads bison 3.7.6, builds it and installs it under/usr/local.- You can change the install path with
make bison BISON_INSTALL_PATH=...
- You can change the install path with
make checkruns the unit tests, style-checkers and linters.make formatformats the code.make dbdownloads the axosyslog release tarball and generates the option database.make db AXOSYSLOG_SOURCE_DIR=/path/to/axosyslogcreates a tarball from the state of the axosyslog source dir and generates the option database.make packagecreates the pip package.
Community
You can reach out to the AxoSyslog community on Discord:
Metadata
Release files for axosyslog-cfg-helper 1.28.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 |
|---|---|---|---|---|
| axosyslog_cfg_helper-1.28.0.tar.gz | 59.8 kB | Without provenance | Details for axosyslog_cfg_helper-1.28.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| axosyslog_cfg_helper-1.28.0-py3-none-any.whl | Python 3 | none | any | Details for axosyslog_cfg_helper-1.28.0-py3-none-any.whl |
Total release size: 137.7 kB
Release files / axosyslog_cfg_helper-1.28.0.tar.gz
| Download URL | axosyslog_cfg_helper-1.28.0.tar.gz |
|---|---|
| Size | 59.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
723b6c5c0c344561e161c12e516e0aa0e68e6feed04498d5457019f1e8ca1dc2
|
|
BLAKE2b-256 checksum How to use checksums |
d29255c763d64ab8100009ab05008502cebdc5748dfe55b84093e52b32deb8d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.12.3 Linux/6.17.0-1022-azure
|
Release files / axosyslog_cfg_helper-1.28.0-py3-none-any.whl
| Download URL | axosyslog_cfg_helper-1.28.0-py3-none-any.whl |
|---|---|
| Size | 77.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c80ada462a97d3a7b5dd51b9d62eeb63144306be52f85829df37293de631e98
|
|
BLAKE2b-256 checksum How to use checksums |
85fee8f57f48acc22138b5700b2ada83c5760670e8db10d3132f05d97a0e6658
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.12.3 Linux/6.17.0-1022-azure
|
Security for axosyslog-cfg-helper 1.28.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.