Sphinx AutoSaltSLS provides a way to automatically document Salt .sls files (e.g. states, pillar, reactors, etc) using simple directives in the comments blocks of those files.
A comment block is identified using a block start string (default is ‘###’) and contains all subsequent lines that start with a given comment character (default is ‘#’’). The block ends when a new start string or a non-comment line is read. Directives can be given in the comment block to control how the lines are parsed.
Getting Started
The following steps will walk through how to add AutoSaltSLS to an existing Sphinx project. For instructions on how to set up a Sphinx project, see Sphinx’s documentation on Getting Started.
Installation
AutoSaltSLS can be installed through pip:
pip install sphinxcontrib-autosaltsls
Next, add and configure AutoSaltSLS in your Sphinx project’s conf.py.
extensions.append('sphinxcontrib-autosaltsls')
autosaltsls_sources = {
'states': {
'title': 'States',
'template_path': '_templates/autosaltsls/states',
},
'pillar' : {
'title': 'Pillar'
},
}
The documentation will be built into the location specified by autosaltsls_build_root (defaults to ‘.’)
To configure AutoAPI behaviour further, see the Configuration documentation.
Basic Setup
The absolute minimum setup is to set autosaltsls_sources as a list of directories under your salt fileset area (e.g. /srv/salt) and let the extension index the files it finds. Documentation pages will be created but, unless the sls files have had their document comment blocks enabled, they will say “No content”.
autosaltsls_sources = [
'states',
'pillar',
]
See Comment Block Format for more information on how to enable these.
To Do
Write proper tests
Credits
This project was based on the logic behind both readthedocs/sphinx-autoapi and Jakski/sphinxcontrib-autoyaml, so many thanks to those projects for getting me started.
[~ Dependencies scanned by PyUp.io ~ ]
Metadata
Release files for sphinxcontrib-autosaltsls 0.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sphinxcontrib-autosaltsls-0.7.1.tar.gz | 19.7 kB | Without provenance | Details for sphinxcontrib-autosaltsls-0.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinxcontrib_autosaltsls-0.7.1-py3-none-any.whl | Python 3 | none | any | Details for sphinxcontrib_autosaltsls-0.7.1-py3-none-any.whl |
Total release size: 40.7 kB
Release files / sphinxcontrib-autosaltsls-0.7.1.tar.gz
| Download URL | sphinxcontrib-autosaltsls-0.7.1.tar.gz |
|---|---|
| Size | 19.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52f6cdcec28196611627f26f6d98acf8dc0484d3b7d15636c4774b9c1a919cc3
|
|
BLAKE2b-256 checksum How to use checksums |
c2bf8db6de4e35212031345d3a3b5a5dd12d4d72c843c0a39b0a984e0f7fb0df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.7.1
|
Release files / sphinxcontrib_autosaltsls-0.7.1-py3-none-any.whl
| Download URL | sphinxcontrib_autosaltsls-0.7.1-py3-none-any.whl |
|---|---|
| Size | 21.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
377e8909935df6e73339c10c4ac3fa9f55ec4c8baecf1116133ff13fbf6e2c63
|
|
BLAKE2b-256 checksum How to use checksums |
7f85fce0ed9fcf6444aa0c984df7c72e415cc2832ac4931932ce25596210c98e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.7.1
|
Security for sphinxcontrib-autosaltsls 0.7.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.
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.