Skip to main content

Salt Extension for MySQL

Salt Extension for interacting with MySQL

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-mysql 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-mysql.git

# Change to the repo dir
cd saltext-mysql

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 + MySQL 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!

Metadata

Release files for saltext.mysql 1.1.1

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.mysql 1.1.1
File Size Uploaded Provenance Actions
saltext_mysql-1.1.1.tar.gz 144.6 kB With provenance Details for saltext_mysql-1.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for saltext.mysql 1.1.1
File Interpreter ABI Platform Actions
saltext_mysql-1.1.1-py3-none-any.whl Python 3 none any Details for saltext_mysql-1.1.1-py3-none-any.whl

Total release size: 195.4 kB

Release files / saltext_mysql-1.1.1.tar.gz

Download URL saltext_mysql-1.1.1.tar.gz
Size 144.6 kB
Tags Source
SHA-256 checksum
How to use checksums
870ff502bf1b02eaec98152ec29d5a3150ddd882f3b4cb0be9c847c40ce1d037
BLAKE2b-256 checksum
How to use checksums
0b7b47c201f2c43ad6c09dbfc86ee960431976d9283b3f914656fb31f40f0370
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 27, 2026.

Transparency log

Release files / saltext_mysql-1.1.1-py3-none-any.whl

Download URL saltext_mysql-1.1.1-py3-none-any.whl
Size 50.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
57816fcb81bcbbbb471c563ed4a925e0bca549caf5856a464cdb67facc500c1a
BLAKE2b-256 checksum
How to use checksums
8cb3b460c634af9984a8aeea38a3a61720ab756a82f37d34fe493fad9da9f33f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 27, 2026.

Transparency log

Security for saltext.mysql 1.1.1

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for saltext_mysql-1.1.1.tar.gz

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 Oct 27, 2026.

Transparency log

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.

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