Skip to main content

Salt Extension for HashiCorp Vault

Salt Extension for interacting with Vault (or OpenBao)

Security

If you discover a security vulnerability, please refer to Salt's security guide.

User Documentation

For setup and usage instructions, please refer to the User Documentation.

Contributing

The saltext-vault project welcomes contributions from anyone!

The Salt Extensions guide provides comprehensive instructions on all aspects of Salt extension development, including writing tests, running tests, writing documentation and rendering the docs.

Quickstart

To get started contributing, first clone this repository (or your fork):

# Clone the repo
git clone --origin upstream git@github.com:salt-extensions/saltext-vault.git

# Change to the repo dir
cd saltext-vault

Automatic

If you have installed direnv, copying the included .envrc.example to .envrc and allowing it to run ensures a proper development environment is present and the virtual environment is active.

Without direnv, you can still run the automation explicitly:

make dev  # or python3 tools/initialize.py
source .venv/bin/activate

Manual

Please follow the first steps, skipping the repository initialization and first commit.

Pull request

Always make changes in a feature branch:

git switch -c my-feature-branch

Please ensure you include a news fragment describing your changes. This is a requirement for all user-facing changes (bug fixes, new features), with the exception of documentation changes.

To submit a Pull Request, you'll need a fork of this repository in your own GitHub account. If you followed the instructions above, set your fork as the origin remote now:

git remote add origin git@github.com:<your_fork>.git

Ensure you followed the first steps and commit your changes, fixing any failing pre-commit hooks. Then push the feature branch to your fork and submit a PR.

Ways to contribute

Contributions come in many forms, and they’re all valuable! Here are some ways you can help without writing code:

You can also contribute by:

  • Writing blog posts
  • Sharing your experiences using Salt + HashiCorp Vault on social media
  • Giving talks at conferences
  • Publishing videos
  • Engaging in IRC, Discord or email groups

Any of these things are super valuable to our community, and we sincerely appreciate every contribution!

Release files for saltext.vault 1.8.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for saltext.vault 1.8.0
File Size Uploaded
saltext_vault-1.8.0.tar.gz 432.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for saltext.vault 1.8.0
File Interpreter ABI Platform
saltext_vault-1.8.0-py2.py3-none-any.whl Python 2, Python 3 none any Details

Total release size: 603.6 kB

Release files / saltext_vault-1.8.0.tar.gz

Download URL saltext_vault-1.8.0.tar.gz
Size 432.3 kB
Tags Source
SHA-256 checksum
How to use checksums
0cb488c65438c94b0633916f24c3bed218215eed5a3f864ebdfb1bccf21e0f04
BLAKE2b-256 checksum
How to use checksums
8bc34eb9bd6152188e92eb8a14e59a194277cbec4e02eb8d2fdeef775c4618c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 9, 2026.

Transparency log

Release files / saltext_vault-1.8.0-py2.py3-none-any.whl

Download URL saltext_vault-1.8.0-py2.py3-none-any.whl
Size 171.3 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
6f13e4415351ff024fc5db4579f122aa46ba615ee5c1bab25b1ea141b312f9aa
BLAKE2b-256 checksum
How to use checksums
68f86087ccf2db612dd4eb6a48add5e680a7a44e57364aecc61f0fb1fb036b8a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 9, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.8.0 This release

2 release files

1.7.0

2 release files

1.6.0

2 release files

1.5.0

2 release files

1.4.0

2 release files

1.3.2

2 release files

1.3.1

2 release files

1.3.0

2 release files

1.2.2

2 release files

1.2.1

2 release files

1.2.0

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page