Documentation (Terraform provider) — Firezone

Cited by

Facts read from this source

• Terraform provider Report an error

  “The Firezone Terraform Provider lets you manage Firezone Portal configuration alongside the infrastructure that runs your Gateways.”

• Terraform managed resources Report an error

  “Use Terraform resources for Sites, Resources, Policies, native Groups, Actors, Group memberships, and Gateways.”

• Terraform data sources Report an error

  “Use data sources for existing Sites, Groups, Actors, Clients, authentication providers, and Entra, Google Workspace, or Okta directories.”

• API token setup Report an error

  “Create an API token under Settings → API Tokens in the admin portal. Store it outside your Terraform configuration and export it before you run Terraform”

• Regional endpoints Report an error

  “The endpoint depends on the region of your account: https://rest-api.firezone.dev for Firezone Cloud US and https://eu.rest-api.firezone.dev for Firezone Cloud EU.”

• Terraform import Report an error

  “You can also import supported Portal objects, which lets your team bring an existing Firezone account under Terraform management over time.”

• Gateway token rotation Report an error

  “Change token_rotation_trigger to rotate the token. The value is arbitrary; a date records when your team last requested a rotation.”

• Imported gateway no token Report an error

  “The Firezone API returns a Gateway token only when it creates or rotates that Gateway. An imported Gateway has no usable token in Terraform state.”

• Unmanaged auth providers Report an error

  “Authentication providers and directories. Set them up in the Portal, where an administrator completes the OAuth authorization flow.”

• Unmanaged device enrollment Report an error

  “Device enrollment. Devices can only be enrolled in two ways, either the first time the Device connects to Firezone or using Device sync through a posture provider.”

• Unmanaged service account tokens Report an error

  “Service-account tokens. For now, the Terraform provider does not have a way to to create a service-account token and the token must be created in the Portal.”

• Unmanaged gateway status Report an error

  “Gateway status and metadata. Use the Portal to inspect a Gateway's online state, addresses, and version.”

• Unmanaged account settings Report an error

  “Account Settings. Any changes to your account, such as seat count, must go through the Portal.”

• Unmanaged logs Report an error

  “Logs. Though logs have a REST API endpoint, it is not enabled through the Terraform provider.”

• Unmanaged device posture integrations Report an error

  “Device-Posture integrations. Similar to Authentication and Directory providers, Device-Posture integrations can require interactive authorization and must be done in the Portal.”

• State token warning Report an error

  “Terraform stores Gateway tokens in state. Restrict access to your remote state backend and encrypt it at rest.”

• Group permission example Report an error

  “The example below creates a Site and an internal application, then grants a directory-synced Engineering Group access to it”

2 facts read from this page are not shown because they could not be confirmed on the page as captured.

Scores citing this record

• The DevOps Engineer Identity, access policy & device posture
• The DevOps Engineer Deployment, API & administration
• The IT Lead Deployment, API & administration
• The MSP Technician Deployment, API & administration
• The Operations Manager Identity, access policy & device posture
• The Operations Manager Deployment, API & administration
• The Information Security Officer Identity, access policy & device posture
• The Information Security Officer Deployment, API & administration
• The Skeptic Deployment, API & administration