Skip to main content

Salt Extension for Nebula

Salt Extension for interacting with Nebula

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

# Change to the repo dir
cd saltext-nebula

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 + Nebula 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.nebula 1.2.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.nebula 1.2.0
File Size Uploaded
saltext_nebula-1.2.0.tar.gz 113.5 kB Details

Built distribution (wheel)

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

Total release size: 151.6 kB

Release files / saltext_nebula-1.2.0.tar.gz

Download URL saltext_nebula-1.2.0.tar.gz
Size 113.5 kB
Tags Source
SHA-256 checksum
How to use checksums
5b1e66dd0b9ab466df7c2aebba0fde018de6de59eadca3e9ab9e4843ed9fe550
BLAKE2b-256 checksum
How to use checksums
3fde2d0bf65214385b1195c343bc193c0cb0bdba8461cce0873523eae54efa99
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 Sep 8, 2026.

Transparency log

Release files / saltext_nebula-1.2.0-py2.py3-none-any.whl

Download URL saltext_nebula-1.2.0-py2.py3-none-any.whl
Size 38.1 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
283baed6380df87fa04acf90e4515b9965cb234276dafa384ba24b0edcac5bd6
BLAKE2b-256 checksum
How to use checksums
2d861644937896be1e7116f00856582b329d6a59739b7cc0527d38d950484509
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 Sep 8, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.2.0 This release

2 release files

1.1.0

2 release files

1.0.2

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