cloudcoil-models-velero
Versioned velero models for cloudcoil.
🔧 Installation
Using uv (recommended):
# Install with Velero support
uv add cloudcoil.models.velero
Using pip:
pip install cloudcoil.models.velero
💡 Examples
Using Velero Models
from cloudcoil import apimachinery
import cloudcoil.models.velero.v1 as velero
# Create a Backup
backup = velero.Backup(
metadata=apimachinery.ObjectMeta(name="mybackup"),
spec=velero.BackupSpec(
included_namespaces=["default"],
storage_location="default"
)
).create()
# List Backups
for b in velero.Backup.list():
print(f"Found Backup: {b.metadata.name}")
Using the Fluent Builder API
Cloudcoil provides a powerful fluent builder API for Velero resources:
from cloudcoil.models.velero.v1 import Backup
# Create a Backup using the fluent builder
backup = (
Backup.builder()
.metadata(lambda metadata: metadata
.name("mybackup")
.namespace("velero")
.labels({"app": "myapp"})
)
.spec(lambda spec: spec
.included_namespaces(["default", "kube-system"])
.storage_location("default")
.ttl("72h")
.hooks(lambda hooks: hooks
.resources(lambda resources: resources.add({
"name": "my-hook",
"included_namespaces": ["default"]
}))
)
)
.build()
)
Using the Context Manager Builder API
For complex backup configurations, you can use the context manager-based builder:
from cloudcoil.models.velero.v1 import Backup
# Create a Backup using context managers
with Backup.new() as backup:
with backup.metadata() as metadata:
metadata.name("mybackup")
metadata.namespace("velero")
with backup.spec() as spec:
spec.included_namespaces(["default", "kube-system"])
spec.storage_location("default")
spec.ttl("72h")
with spec.hooks() as hooks:
with hooks.resources() as resources:
with resources.add() as resource:
resource.name("my-hook").included_namespaces(["default"])
with resources.add() as resource:
resource.name("another-hook").included_namespaces(["default"])
final_backup = backup.build()
📚 Documentation
For complete documentation, visit cloudcoil.github.io/cloudcoil
📜 License
Apache License, Version 2.0 - see LICENSE
Metadata
Release files for cloudcoil.models.velero 1.18.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 | |
|---|---|---|---|
| cloudcoil_models_velero-1.18.2.0.tar.gz | 108.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloudcoil_models_velero-1.18.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 152.5 kB
Release files / cloudcoil_models_velero-1.18.2.0.tar.gz
| Download URL | cloudcoil_models_velero-1.18.2.0.tar.gz |
|---|---|
| Size | 108.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6dbea94d6a6b5fbbfe3e974b327c0bcc416cb3c6e7531d253b7ff7dc1984fdbb
|
|
BLAKE2b-256 checksum How to use checksums |
5d0688cfb4e9e9464885ae48d50c0cbd77e4934b57f0b29726364ad32cac20a6
|
| 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 7, 2026.
Transparency logRelease files / cloudcoil_models_velero-1.18.2.0-py3-none-any.whl
| Download URL | cloudcoil_models_velero-1.18.2.0-py3-none-any.whl |
|---|---|
| Size | 44.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed81106ae2b2e9f21916a0fa6a9eef3beed4807bc9696d0de483b14c1793ec58
|
|
BLAKE2b-256 checksum How to use checksums |
52382e5d937db43ffecf3eba94ad1d5f17950c3c49f14b4e070bef6b28cb747f
|
| 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 7, 2026.
Transparency log