Manage Kestra User Tenant Access with the Terraform Provider
For the complete documentation index, see llms.txt. For a full content snapshot, see llms-full.txt. Append .md to any kestra.io/docs/* URL for plain Markdown.

Terraform Resource: kestra_user_tenant_access

Grants a user access to a tenant.

Since Kestra 2.0 tenant access is a prerequisite rather than something granted as a side effect: a tenant-scoped write such as kestra_user_group_membership resolves the user through a tenant access check and rejects it otherwise. Declare this resource for every user that a tenant-scoped resource refers to, and make those resources depend on it.

Destroying this resource revokes the user’s access to the tenant. Removing a kestra_user_group_membership does not, since other memberships and tokens may still rely on the access.

Example usage

resource "kestra_user_tenant_access" "example" {
  user_id = "4by6NvSLcPXFhCj8nwbZOM"
}


# Tenant access is a prerequisite for tenant-scoped resources: grant it first,
# then have those resources depend on it.
resource "kestra_user_group_membership" "example" {
  user_id  = "4by6NvSLcPXFhCj8nwbZOM"
  group_id = "2ZQwf5Lj9pUyKxRtBvNm8H"


  depends_on = [kestra_user_tenant_access.example]
}

Schema

Required

  • user_id (String) The id of the user granted access to the tenant.

Read-Only

  • id (String) The ID of this resource.
  • tenant_id (String) The tenant id.

Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

terraform import kestra_user_tenant_access.example {{user_id}}

Was this page helpful?