To enable data-collector pass data-collector.yaml YAML format:
data_collector_base_directory: "<base directory for data collection>"
collect_data_function: "<import path for data collection method>"
collect_pod_logs: true|false # bool whether to collect logs if resource is a pod
YAML Example ocp_utilities/data-collector.yaml:
data_collector_base_directory: "collected-info"
collect_data_function: "data_collector.collect_data"
collect_pod_logs: true
Either export path to yaml file in OPENSHIFT_PYTHON_WRAPPER_DATA_COLLECTOR_YAML or set data_collector in your py_config
The environment variable takes precedence over py_config.
To use dynamic base directory, export OPENSHIFT_PYTHON_WRAPPER_DATA_COLLECTOR_DYNAMIC_BASE_DIR
Example:
data_collector_base_directory = "/data/results/collected-info"
OPENSHIFT_PYTHON_WRAPPER_DATA_COLLECTOR_DYNAMIC_BASE_DIR = "dynamic_collector_test_dir"
Result: /data/results/dynamic_collector_test_dir/collected-info
1 maintainer
Metadata
1 maintainer
Release files for openshift-python-wrapper-data-collector 2.0.15
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 |
|---|---|---|---|---|
| openshift_python_wrapper_data_collector-2.0.15.tar.gz | 8.2 kB | Without provenance | Details for openshift_python_wrapper_data_collector-2.0.15.tar.gz |
Release files / openshift_python_wrapper_data_collector-2.0.15.tar.gz
| Download URL | openshift_python_wrapper_data_collector-2.0.15.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f58c353daf3a360cfee9349b79f191180bf66d7b87a5f54301f240d63248f6cc
|
|
BLAKE2b-256 checksum How to use checksums |
3b5d7d0652c649da05ffbe6e610e8d642fd88f1274a3f16cf8fe06df75a4c17f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Security for openshift-python-wrapper-data-collector 2.0.15
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.
