The Kvindo Terraform provider lets you manage cloud resources declaratively, against the same API as the console and the CLI. Resources use the familiar metadata / spec shape.

1. Add the provider

Declare it in your configuration, then run terraform init:

2. Configure authentication

Authenticate with a bearer token — create one in the console under IAM → Tokens → Create token. Pass it via a variable (or the KVINDO_TOKEN environment variable). The endpoint is optional and defaults to https://cloud-api.kvindo.com (the https://cloud-api.kvindo.ru mirror can be used instead).

3. Write a resource

Each resource has a metadata block and a spec block, mirroring the API. Resources are placed in a folder via metadata.folder_id; the easiest way is to look up the organization's default folder with a datasource and reference its id. The provider has no name resolution, so hosting_provider_id is likewise resolved from a kvindo_hosting_provider datasource — g-ru-msk-1 here (run kc get provider for others):

4. Apply

Links

• Provider documentation (Terraform Registry)

---

Related pages

More in this section

• Design ideas
• Examples

Reference

• Kvindo provider on the Terraform Registry
• Provider source on GitHub