Skip to content

qumulo_portal_spoke_root (Resource)

Manages a root directory pair within a portal spoke relationship.

In most cases, qumulo_portal and qumulo_portal_root are simpler and recommended. Use this resource only when the hub and spoke clusters cannot both be reached from the network where Terraform runs.

Each root maps a local spoke directory to a remote hub directory. After adding a root on the spoke, the hub must authorize it via the qumulo_portal_hub_root resource.

Example Usage

Installation

terraform {
  required_providers {
    qumulo = {
      source  = "qumulo-terraform-registry.s3.us-east-1.amazonaws.com/qumulo/qumulo"
      version = "~> 1.0"
    }
  }
}

resource "qumulo_portal_spoke_root" "data" {
  connection_profile = "spoke"

  spoke_id        = qumulo_portal_spoke.main.id
  spoke_root_path = "/cache/data"
  hub_root_path   = "/data"
}

Schema

Required

  • connection_profile (String) Name of a connection profile defined in the provider block.

Connection profiles centralize cluster credentials at the provider level. Define profiles in the provider block:

provider "qumulo" {
  connection_profiles = [
    {
      name                 = "prod"
      endpoint             = "https://cluster.example.com:8000"
      username             = "admin"
      password             = var.cluster_password
      insecure_skip_verify = true  # For self-signed certificates
    }
  ]
}
- hub_root_path (String) The remote directory path on the hub cluster. - spoke_id (Number) The ID of the parent spoke portal. - spoke_root_path (String) The local directory path on the spoke cluster.

Read-Only

  • authorized (Boolean) Whether the hub has authorized this root for access.
  • id (String) Composite ID: spoke_id/local_root_file_id.
  • local_root (String) The spoke directory file ID.
  • remote_root (String) The hub directory file ID.