Convection Plugin - Secrets - PassDB
Password Generator and Storage
Physical Storage
If the Secret Store Name contains slashes, it is assumed as a path, and placed as $STORAGE_ROOT/$STORE_NAME (ex: (/data)/(my/secret/store)). If it does not contain slashes, it is stored at $STORAGE_ROOT/secrets/$STORE_NAME (ex (/data)/(my.secret.store))
Data is stored all in a single file.
Data Format
{
"metadata": { <plugin metadata> },
"config": { <configuration data> },
"store": { <passdb in k:v form>},
"stats": {
"reads": <number of reads performed since creation>,
"writes": <number of writes performed since creation>
}
}
Note that the Stats data for Reads may not be accurately represented if a number reads happen, but a write does not occur before the Convection Secrets Manager is shutdown/restarted. These stats are held in memory until a write occurs, and so the stat for reads since the last write would be lost on stop/restart. Write stat should always be accurate. The Read stat will be accurate for the duration of the service running (assuming no writes), however.
Secret Store Args
These arguments are required when a new PassDB Store is created.
{
"default": {
"length": <default password length>,
"letters": <default password letters>
}
}
During creation you should pass --store-arg '{ "default": { ... } }' to configure these values
Secrets Args
Create/Modify
secret_name: Name of Entry to Create/Modifysecret_value: [OPTIONAL] Password. If empty, a password will be generated.length: [OPTIONAL] Password Length. If empty,20.value_type: [OPTIONAL] Password Value Type. If empty,printable.
Get/Destroy
secret_name: Name of Secret to View/Destroy
Password Value Types
This is a selection of which characters will be available in the password that is generated. This parameter is based on entries from the string class. Its value may be one of:
printable: Any printable characterascii_letters: Upper and Lowercase ASCII charactersdigits: Numbers only
Metadata
Release files for convection-plugin-secrets-passdb 1.0.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 | |
|---|---|---|---|---|
| convection-plugin-secrets-passdb-1.0.0.tar.gz | 57.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| convection_plugin_secrets_passdb-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 76.2 kB
Release files / convection-plugin-secrets-passdb-1.0.0.tar.gz
| Download URL | convection-plugin-secrets-passdb-1.0.0.tar.gz |
|---|---|
| Size | 57.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c61cc019213477e7fd1d44050827ee5c7d17ce09a453dca51587a1c1bfb45b79
|
|
BLAKE2b-256 checksum How to use checksums |
200bbaa2a6af17386e75025cdf7b902907c1055e5b5b074b3b23992b4e79ca20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.2
|
Release files / convection_plugin_secrets_passdb-1.0.0-py3-none-any.whl
| Download URL | convection_plugin_secrets_passdb-1.0.0-py3-none-any.whl |
|---|---|
| Size | 18.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f82255a10b138088d9f810303ecee1a63071f641ee227181ee41ec3048b3d181
|
|
BLAKE2b-256 checksum How to use checksums |
e7cfb7e7eef845c451f0ab5022672ee3d9f1a38c220b270c23cfcbb403ed6030
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.2
|
Security for convection-plugin-secrets-passdb 1.0.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.