flyteproto
Flyteproto is a collection of generated protocol buffer bindings for kubernetes generated protobuf definitions.
Contents
k8s
Generated protobuf code (currently python only), complete with imports synced from k8s.io/apimachinery in kubernetes/apimachinery
k8s.io
Core and imported protobuf definitions in a path that matches their declared packages. Use these to generate protobufs that import the core kubernetes protos.
Usage
Run generate.sh to regenerate protobuf code.
To use kubernetes protobuf definitions in your own protobufs, pass the k8s.io dir as an input directory to protoc:
protoc -I=k8s.io/ [OPTION] PROTO_FILES2 maintainers
Metadata
2 maintainers
Release files for k8s-proto 0.0.3
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 |
|---|---|---|---|---|
| k8s-proto-0.0.3.tar.gz | 51.5 kB | Without provenance | Details for k8s-proto-0.0.3.tar.gz |
Release files / k8s-proto-0.0.3.tar.gz
| Download URL | k8s-proto-0.0.3.tar.gz |
|---|---|
| Size | 51.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddcffbd275fadf656dcbd22fcce7c9041042ad81e19664753dde8dd0d0287749
|
|
BLAKE2b-256 checksum How to use checksums |
5b60daff2df8df7f0eeb2ff428159e3913e7d56b47097ff3d4f50659a264ffbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/18.5 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.10
|
Security for k8s-proto 0.0.3
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.
