Building Your First Data Source
Part 2 of 5: add a read-only data source that lets Terraform query servers without managing them.
Building a Provider from ScratchPractical guides for building a provider with Pyvider. Start with the foundation, then add one capability at a time.
Part 1 of 5: set up a project, define a provider class, and implement a full CRUD resource.
Each guide continues from the provider you built before it.
Part 2 of 5: add a read-only data source that lets Terraform query servers without managing them.
Building a Provider from ScratchPart 3 of 5: add a callable provider function and use it to drive a resource name — tying the full series together.
Building a Provider from ScratchPart 4 of 5: add an ephemeral resource for short-lived credentials — the open/renew/close lifecycle explained.
Building a Provider from ScratchPart 5 of 5: package your provider into a single-file binary with Flavorpack — no Python, no venv, no install step for your users.
Building a Provider from ScratchPart 6: the two protocol 6.11 component types you're most likely to reach for — an imperative operation that isn't a resource, and a way to ask what already exists. Both running, against Terraform 1.15.
Building a Provider from ScratchPart 7: add selectable, advisory guidance to a provider, package it, and prove it through TofuSoup's direct lane and OpenTofu's experimental lint validation.
Building a Provider from Scratch