Qbee Terraform Provider¶
Managing device fleet configurations through the Qbee web UI works well at small scale, but clicks don't scale and manual configuration is error-prone. With the Qbee Terraform Provider, you store your fleet configuration in version control, review changes before they deploy, and apply the same setup reliably across dev, test, and production — all through your CI/CD pipeline, without anyone logging in and clicking.
If you are new to the provider, start with Getting Started. Use the table below to navigate to the right document for your current goal.
Find What You Need¶
| I want to... | Go to |
|---|---|
| Install the provider, authenticate, and distribute my first file to a device | Getting Started |
| Browse available resources or look up their configuration arguments | Provider Reference Documentation |
| Troubleshoot an error or unexpected behavior | Troubleshooting |
Quick Example¶
# Configure the provider
provider "qbee" {
username = var.qbee_username
password = var.qbee_password
}
# Upload a file to the Qbee file manager
resource "qbee_filemanager_file" "app_config" {
path = "/configs/app.conf"
sourcefile = "${path.module}/app.conf"
file_sha256 = filesha256("${path.module}/app.conf")
}
# Distribute the file to all devices tagged "example"
resource "qbee_filedistribution" "example" {
tag = "example"
extend = true
files = [
{
templates = [
{
source = "/configs/app.conf"
destination = "/etc/app/app.conf"
is_template = false
}
]
}
]
}
terraform init # Download the provider
terraform plan # Preview changes
terraform apply # Apply configuration
See Also¶
| I want to... | Resource |
|---|---|
| Learn about the Qbee platform | Qbee Documentation |
| View the provider on Terraform Registry | registry.terraform.io/providers/qbee-io/qbee |
| Use the Qbee CLI for ad-hoc operations | qbee-cli |
| Use the Qbee REST API | REST API |