Kvindo™ Cloud Docs
A Transaction creates a whole set of resources atomically: either all of them are accepted and reconciled, or none are. Its spec carries one array per resource type (folders, users, VMs, VPCs, load balancers, and so on), so an entire environment can be described in a single declarative document.
• Child resources — spec holds a typed array for each resource kind (folders, users, vms, …); each entry is a normal resource definition
• Atomicity — the transaction is validated as a whole; if any resource is invalid, the entire transaction is rejected
• Delete behaviour — deleteResourcesOnTransactionDelete controls whether deleting the transaction also deletes the resources it created
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| Delete resources on delete | spec.deleteResourcesOnTransactionDelete |
spec.delete_resources_on_transaction_delete |
No | boolean | — | No | Whether deleting the transaction also deletes the resources it created |
| Child resource arrays | spec.<type>s |
spec.<type>s |
Yes | list of <type> resources | — | No | One array per resource kind: folders, users, accessPolicies, vms, vpcs, loadbalancers, … |
Terraform
Python SDK
kc CLI
Examples
Guides
More in this section