robocorp-vault
robocorp-vault is a library that provides read and write access to the Vault in Robocorp Control Room, which can be used to store and retrieve secret values such as passwords.
Getting started
A secret consists of a name, an optional description, and a map of keys and values. For instance, one secret can be login credentials for a website, which includes both a username and a password:
from robocorp.tasks import task
from robocorp import vault
@task
def inspect_secret():
secret = vault.get_secret("login_credentials")
print("Secret name:", secret.name)
print("Secret description:", secret.description)
print("Secret keys:", secret.keys())
print("Secret value:", secret["username"])
Guides
Further user guides and tutorials can be found in Robocorp Docs.
API Reference
Explore our API for extensive documentation.
Changelog
A list of releases and corresponding changes can be found in the changelog.
Release files for robocorp-vault 1.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| robocorp_vault-1.4.1.tar.gz | 10.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| robocorp_vault-1.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.5 kB
Release files / robocorp_vault-1.4.1.tar.gz
| Download URL | robocorp_vault-1.4.1.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab4b41dae5b2a305ef6b4ab70b5049c463190445680494003351fdfcabd96159
|
|
BLAKE2b-256 checksum How to use checksums |
33b21ff7aad1a631e27ae1ac10281dce30dbc4e51bd1d02218c0a6c2183d399a
|
| 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 Aug 23, 2026.
Transparency logRelease files / robocorp_vault-1.4.1-py3-none-any.whl
| Download URL | robocorp_vault-1.4.1-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
717a18ce38044d682edff1efb9de8aeb1e3d136209955bd8caeb858e2bdebe9e
|
|
BLAKE2b-256 checksum How to use checksums |
e420668b46b04cc6ff69153669dc802d21d05e9785f87f9233ca8cc95ca8a7b1
|
| 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 Aug 23, 2026.
Transparency log