deepflow-kms-cli
Replace <KMS:KEY_NAME> placeholders in env files, and reset the single admin password.
pip install deepflow-kms-cli
export KMS_BASE_URL=https://kms.deepflowagent.com
export KMS_APP_ID=app_xxxxxxxx
export KMS_APP_SECRET=sk_xxxxxxxx
deepflow_kms_cli inject \
--in private/env/server.env.production \
--out /run/opendesk/server.env
See the project integration doc for IP allowlists and placeholder rules.
Metadata
Release files for deepflow-kms-cli 0.1.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 | |
|---|---|---|---|---|
| deepflow_kms_cli-0.1.0.tar.gz | 3.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deepflow_kms_cli-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.1 kB
Release files / deepflow_kms_cli-0.1.0.tar.gz
| Download URL | deepflow_kms_cli-0.1.0.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44a7e6fa9ba816adbe2e3eee81ee088bc6b6d1a4499eb0c11ea50d9d30d23217
|
|
BLAKE2b-256 checksum How to use checksums |
403331a7081c3162267341585f3a854f30b98cf82304fef77c64198ba7be8dde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / deepflow_kms_cli-0.1.0-py3-none-any.whl
| Download URL | deepflow_kms_cli-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6949a788da5db751665dcac158c40d44e5906c414b7fe412e6631a5634ff07d2
|
|
BLAKE2b-256 checksum How to use checksums |
4046bf7d69cf01ca641ab36ff73fc35d8c98f644d0d77c186a3c47c4754c7ced
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for deepflow-kms-cli 0.1.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.