How linode/terraform-provider-linode works
This is a Terraform provider for provisioning and querying Linode cloud infrastructure. The principal workflow runs from Terraform configuration through the provider protocol and registered resource or data-source handlers, which translate Terraform values into Linode API requests and return results for Terraform state. The tree shows broad coverage across compute, networking, managed services, object storage, and account capabilities. Sampled source confirms instance, database, and bucket operations; wiring for other resource families is inferred only at the provider registration level, so their individual API call paths are not expanded here.
Main entry points: framework_provider.go Framework provider · main.go Protocol server · framework_resource.go PostgreSQL databases · resource.go Instances
Components 18
Provider entry
- Protocol server
main.go - Framework provider
linode/framework_provider.go - SDK provider
linode/provider.go
Compute and Kubernetes
- Instances
linode/instance/resource.go - Kubernetes clusters
linode/lke/cluster.go - Instance disks and config
linode/instanceconfig/resource.go
Networking and security
- VPC and IP
linode/vpc - Firewalls
linode/firewall - Domains and DNS
linode/domain
Managed services
- MySQL databases
linode/databasemysqlv2/framework_resource.go - PostgreSQL databases
linode/databasepostgresqlv2/framework_resource.go - Database catalog
linode/databaseengines - Object storage
linode/objbucket/resource.go - Monitoring and logs
linode/monitoralertdefinition - Account and IAM
linode/iamuser
Provider support
- Shared helpers
linode/helper
Other components
- Terraform
- Linode API
Connections 23
- Terraform → Protocol server: configures provider
- Protocol server → Framework provider: serves protocol
- Protocol server → SDK provider: muxes protocol
- Framework provider → Instances: registers resources
- Framework provider → Kubernetes clusters: registers resources
- Framework provider → Instance disks and config: registers resources
- Framework provider → VPC and IP: registers resources
- Framework provider → Firewalls: registers resources
- Framework provider → Domains and DNS: registers resources
- Framework provider → MySQL databases: registers resources
- Framework provider → PostgreSQL databases: registers resources
- Framework provider → Database catalog: registers resources
- Framework provider → Object storage: registers resources
- Framework provider → Monitoring and logs: registers resources
- Framework provider → Account and IAM: registers resources
- Instances → Linode API: creates and updates
- Kubernetes clusters → Linode API: manages clusters
- MySQL databases → Linode API: manages databases
- PostgreSQL databases → Linode API: manages databases
- Object storage → Linode API: manages buckets
- Database catalog → Shared helpers: uses shared logic
- PostgreSQL databases → Shared helpers: uses shared logic
- Linode API → Terraform: returns resource data