cleura-openstackclient
Conveniently installs OpenStack clients for Cleura Cloud.
Purpose
By pip-installing this meta-package into a virtual environment (venv), you populate your environment with OpenStack clients whose versions are expected to work with Cleura Cloud.
This package provides no functionality of its own; it only installs dependencies.
Installation
To install from PyPI, run:
# using pip
pip install cleura-openstackclient==0.0.12
# using pipx
pipx install --include-deps cleura-openstackclient==0.0.12
To install directly from the repository, run:
# using pip
pip install git+https://github.com/cleura/cleura-openstackclient@v0.0.12
# using pipx
pipx install --include-deps git+https://github.com/cleura/cleura-openstackclient@v0.0.12
Then, invoke the openstack command provided by the python-openstackclient package.
License
Just like all other OpenStack client packages, cleura-openstackclient uses the Apache 2 license.
See LICENSE.txt for details.
Release files for cleura-openstackclient 0.0.12
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 | |
|---|---|---|---|---|
| cleura_openstackclient-0.0.12.tar.gz | 17.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cleura_openstackclient-0.0.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.6 kB
Release files / cleura_openstackclient-0.0.12.tar.gz
| Download URL | cleura_openstackclient-0.0.12.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15d94aab7ed4a17dec3c0730512f48ec5570fa9a3ff6300a3644c59f7868a5d6
|
|
BLAKE2b-256 checksum How to use checksums |
df9acf95a64661998d0732860b9c8a8f427fd691feed3aa038748917d66818e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / cleura_openstackclient-0.0.12-py3-none-any.whl
| Download URL | cleura_openstackclient-0.0.12-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
62bd4dd4fd27310651a7593fc0108dd38b624442b6197911364e5b5af57bf412
|
|
BLAKE2b-256 checksum How to use checksums |
16f2e5c214471dd69c792dc2e3f6844042fb4955dec4555b3b0d9f3e015e8ad5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logSecurity for cleura-openstackclient 0.0.12
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cleura_openstackclient-0.0.12.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logA 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.
