naislinter
A simple Python script to validate that your NAIS yaml file adheres to the NAIS specifications.
Local installation
$ pip install naislinter
Local usage
$ naislinter nais.yaml
Will print any path in the config tree that falls outside of the spec and return a non-zero code if any were encountered.
Returns 0 if the file is valid according to the NAIS specifications.
Limitations
This does not validate value types, this is not in scope as nais/deploy verifies types and rejects
a deployment if the NAIS yaml file is malformed in this fashion.
Additionally, this tool requires a fully formed NAIS yaml file, after any template injections.
A file containing {{ image }} will therefore fail, unless the variable has been injected.
Finally, in its current state, the tool is unable to verify objects within lists. For instance:
spec:
env:
- name: KEY
value: value
- name: ANOTHER_KEY
value: another_value
key_outside_of_spec: hello!
key_outside_of_spec will not be caught as an error since it's in an object within a list.
Metadata
Release files for naislinter 1.0.2
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 |
|---|---|---|---|---|
| naislinter-1.0.2.tar.gz | 2.6 kB | Without provenance | Details for naislinter-1.0.2.tar.gz |
Release files / naislinter-1.0.2.tar.gz
| Download URL | naislinter-1.0.2.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed8e61b171d1a8c8579597982548e3eae8b62271a8d8950acc65904200fec979
|
|
BLAKE2b-256 checksum How to use checksums |
ccabede5c3b9690ec5ad63af8f9c406b875f5c31038ea25603692f2dc0126dbf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.0
|
Security for naislinter 1.0.2
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.