Skip to main content

Salt Extension for Pushover

Salt Extension for interacting with Pushover

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

# Change to the repo dir
cd saltext-pushover

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 + Pushover 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.pushover 2.0.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.pushover 2.0.0
File Size Uploaded
saltext_pushover-2.0.0.tar.gz 68.1 kB Details

Built distribution (wheel)

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

Total release size: 84.7 kB

Release files / saltext_pushover-2.0.0.tar.gz

Download URL saltext_pushover-2.0.0.tar.gz
Size 68.1 kB
Tags Source
SHA-256 checksum
How to use checksums
4c5c3b6137d44b56ca7a46939f9beef007d93f1dfa91232c422e91e8aa6624f4
BLAKE2b-256 checksum
How to use checksums
552a5fe08ea82f21d48988806c44fcf978f164271269fba2cf908516c3b0f2f7
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 Mar 17, 2026.

Transparency log

Release files / saltext_pushover-2.0.0-py2.py3-none-any.whl

Download URL saltext_pushover-2.0.0-py2.py3-none-any.whl
Size 16.6 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
c73378117570fafb4c4ae5d3ef6a9e679fbd09ecb1589f67e674d4588d8a3cf4
BLAKE2b-256 checksum
How to use checksums
3b18a068a54c12b61ebd6caa78842abe8d1f381529ea52d684c4ad60fc11146e
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 Mar 17, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2.0.0 This release

2 release files

1.0.1

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