nsot_sync
The goal of nsot_sync is to translate from a driver (local computer networks or another vendor’s IPAM) to native NSoT resources.
It has been written to make adding extra drivers easy, based on a simple contract.
For Quickstart and other documentation, check out the docs.
TODO
Write tests
Write out driver contract
Driver Contract
Unfinished, reminder list for writing the real contract out
Every resource must contain an ‘attributes’ key, even if empty dict
Metadata
Release files for nsot_sync 0.5.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 |
|---|---|---|---|---|
| nsot_sync-0.5.1.tar.gz | 8.8 kB | Without provenance | Details for nsot_sync-0.5.1.tar.gz |
Release files / nsot_sync-0.5.1.tar.gz
| Download URL | nsot_sync-0.5.1.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
74eb690a8fcfa3596cf15458387de495f2d28c53ca999c827ca277f95154c083
|
|
BLAKE2b-256 checksum How to use checksums |
d5217f19e846e677304cbff78ab88f900bcf8c777016f5809054b50f224d8c3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nsot_sync 0.5.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.