Skip to main content

Salt Extension for Suse Ip

Salt Extension for interacting with SUSE IP module

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 module docstrings (for now, documentation is coming!).

Contributing

The saltext-suse-ip 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-suse-ip.git

# Change to the repo dir
cd saltext-suse-ip

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 + Suse Ip 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.suse-ip 0.1.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.suse-ip 0.1.0
File Size Uploaded Provenance Actions
saltext_suse_ip-0.1.0.tar.gz 69.8 kB Without provenance Details for saltext_suse_ip-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for saltext.suse-ip 0.1.0
File Interpreter ABI Platform Actions
saltext_suse_ip-0.1.0-py2.py3-none-any.whl Python 2, Python 3 none any Details for saltext_suse_ip-0.1.0-py2.py3-none-any.whl

Total release size: 86.4 kB

Release files / saltext_suse_ip-0.1.0.tar.gz

Download URL saltext_suse_ip-0.1.0.tar.gz
Size 69.8 kB
Tags Source
SHA-256 checksum
How to use checksums
1830ce98851ae7c7bb5aaf74e2afd6799eaa6cfbeefee1d0f201eb84aefa2857
BLAKE2b-256 checksum
How to use checksums
b269b5570b135fb0200d7a505ac25c063e55312db61c68100797fb014690c279
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.13

Release files / saltext_suse_ip-0.1.0-py2.py3-none-any.whl

Download URL saltext_suse_ip-0.1.0-py2.py3-none-any.whl
Size 16.7 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
8bca1d01d4927bfb167ebfeac3196493adbc7ae51d9de8a692753a7d1e941247
BLAKE2b-256 checksum
How to use checksums
c7d16b029937f22f69a38a7679b1bbc4f151d8f33cdf5e031a9247094ed20e59
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.13

Security for saltext.suse-ip 0.1.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

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