certbot_deployer_vsphere
Certbot Deployer plugin for deploying web certificates for the vSphere web UI via Certbot "deploy hook".
Requires
- Python 3.9+
- vSphere 7 or 8
Installation
You can install with pip:
python3 -m pip install certbot_deployer_vsphere
Or install from source:
git clone <url>
pip install certbot_deployer_vsphere
Usage
Examples
Examples assume the tool is being run as a Certbot deploy hook, and the environment variable RENEWED_LINEAGE points to the live certificate directory just updated by Certbot.
To deploy the certificate bundle indicated by $RENEWED_LINEAGE to $VSPHEREHOST:
certbot-deployer-vsphere --user $VSPHEREUSER --password $VSPHEREPASSWORD --host $VSPHEREHOST
Config
It is recommended that you store the password in the Certbot Deployer configuration file (/etc/certbot_deployer/certbot_deployer.conf) with appropriate permissions rather than providing it as an argument and leaving it visible in the process list
{
[...],
"vsphere": {
"user": "vsphereuser",
"password": "vspherepassword",
"host": "vspherehost",
}
}
Reference
usage: certbot-deployer vsphere [-h] --user USER --password PASSWORD --host
HOST [--tls-no-verify]
Certbot Deployer plugin for deploying web certificates to VSphere
options:
-h, --help show this help message and exit
--user USER, -u USER vSphere API user
--password PASSWORD, -p PASSWORD
vSphere API password
--host HOST, -H HOST vsphere host to target
--tls-no-verify Skip TLS verification of the API endpoints e.g. if
deploying Certbot certificates over self-signed
certificates currently in-place
Contributing
Merge requests are welcome. You should probably open an issue first to discuss what you would like to change.
To run the test suite:
# Dependent targets create venv and install dependencies
make
Please make sure to add/update tests along with any changes.
License
License :: OSI Approved :: MIT License
Metadata
Release files for certbot-deployer-vsphere 0.1.2
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 |
|---|---|---|---|---|
| certbot_deployer_vsphere-0.1.2.tar.gz | 7.2 kB | Without provenance | Details for certbot_deployer_vsphere-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| certbot_deployer_vsphere-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for certbot_deployer_vsphere-0.1.2-py3-none-any.whl |
Total release size: 14.2 kB
Release files / certbot_deployer_vsphere-0.1.2.tar.gz
| Download URL | certbot_deployer_vsphere-0.1.2.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00cdf417f87f0cde0658df11e11280a41d390c4d43ab334707c117b851250c3d
|
|
BLAKE2b-256 checksum How to use checksums |
dd7038dc081233d1f5024aaee62ba953a2057a882b3c80c8df22be71e63a8d65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Release files / certbot_deployer_vsphere-0.1.2-py3-none-any.whl
| Download URL | certbot_deployer_vsphere-0.1.2-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a65a57291236c21383996d5f27b36340e1b76705134a431cd53fe3fd2e96b5c
|
|
BLAKE2b-256 checksum How to use checksums |
beb92ea27207f634acaf500b6671c9142dad5d8766fe0386f94564ad3fd7f904
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Security for certbot-deployer-vsphere 0.1.2
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.