API-v3
Version 3 API for OneVizion
This is a wrapper for simplifying API connection to a OneVizion system.
Install with
pip install onevizion
The Parameters.json file is not necessary, but we added in, since we use it for our scripts, and it keeps hardcoded logins and things our of a script.
All of our scripts use a Parameters.json file, which includes usernames and passwords along with URLs and other configuration. This lets us test locally, then copy a script up unedited, to the production server or UAT server, and it will work correctly using parameters for that system.
That file looks like this:
{
"trackor.onevizion.com": {
"url":"trackor.onevizion.com",
"UserName": "jsmith",
"Password": "xxxxxxxxxxxx"
},
"Veracode": {
"UserName": "jsmith@onevizion.com",
"Password": "xxxxxxxxx"
},
"Folders": {
"Archiva": "/opt/tomcat/data/repositories/releases",
"Git": "/Users/jsmith/GitHub/IKAM/ov"
},
"SMTP_ESRI": {
"UserName": "jsmith@onevizion.com",
"Password": "xxxxxxxxxxxxx",
"Server": "smtp.office365.com",
"Port": "587",
"Security": "STARTTLS",
"To": "jsmith@onevizion.com"
},
"SMTP": {
"UserName": "jsmith@onevizion.com",
"Password": "xxxxxxxxxxxx",
"Server": "smtp.office365.com",
"Port": "587",
"Security": "STARTTLS",
"To": "jsmith@onevizion.com"
},
"AWSCredentials": {
"AccessKey": "AOJBFJQEBFJQEFJEEJBFEJF",
"SecretAccessKey":"jlknf3kj4nr34rjnwj4nrwj4werwe"
}
}
The idea is that you have a token, like "STMP" , or "trackor.onevizion.com", and it has all the relavent parameter info.
We tried to add some automatic Logging and Messaging for all API connections. It is optional, but can cut down on lines of code if you want to use it. To implement this, we created a Config stucture so you can pass parameters to ALL instances of the classes you create. This is not elegant, but it cut down on necessary lines of code and made readability much better.
This Config structure is used for Messaging by setting the "Verbosity" item to a number. Vebosity = 0 gives only error messaging, Verbosity = 1 gives a little more information. The higher the number, the more information, although, at teh time of this writing, 2 is the highest used. for example:
onevizion.Config["Verbosity"] = 1
The Logging part is handled in onevizion.Config["Trace"]. Trace is an OrderedDict. This can be used however you need to get a list of Messaging that hapened during the script's run.
You can find samples of scripts using this library at api-samples
Releasing
Maintainers: see RELEASING.md.
1 maintainer
Release files for onevizion 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| onevizion-1.2.0.tar.gz | 61.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| onevizion-1.2.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 97.6 kB
Release files / onevizion-1.2.0.tar.gz
| Download URL | onevizion-1.2.0.tar.gz |
|---|---|
| Size | 61.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86ed2ce5f6c3ac7b05caed96db807f235c9cee40668697ea74d75b472728ee3e
|
|
BLAKE2b-256 checksum How to use checksums |
814f67a31b07de614bbec197086661041d2fe3879a9ff0736604a7c5531ffcda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 24, 2026.
Transparency logRelease files / onevizion-1.2.0-py2.py3-none-any.whl
| Download URL | onevizion-1.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 36.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
1d7012ff816c32e5ea076d77a0527ebce8eb37986b0d588f6383997665ecccd1
|
|
BLAKE2b-256 checksum How to use checksums |
92cdde1724ac695738424c816bd142300981af49ff76233f649067d271be6952
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 24, 2026.
Transparency log
