Skip to content

qumulo_portal_spoke (Resource)

Manages a portal spoke relationship on a Qumulo cluster using the v2 Portal API.

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.

Only one portal relationship can exist between any two clusters. Use qumulo_portal_spoke_root to add directory pairs within the relationship, and qumulo_portal_hub on the hub cluster to accept and authorize roots.

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" "main" {
  connection_profile = "spoke"

  type        = "PORTAL_READ_ONLY"
  hub_address = "10.0.0.1"
}

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_address (String) The hostname or IP address of the hub cluster. - type (String) Portal type: PORTAL_READ_ONLY or PORTAL_READ_WRITE.

Optional

  • hub_port (Number) The port for portal communication on the hub cluster (default: 3713).

Read-Only

  • hub_cluster_uuid (String) The UUID of the hub cluster.
  • hub_id (Number) The ID of the hub portal on the hub cluster.
  • id (Number) The ID of the spoke portal.
  • spoke_cluster_uuid (String) The UUID of this spoke cluster. Used by qumulo_portal_hub to match the pending relationship.
  • state (String) The state of the portal: PENDING, ACCEPTED, or DELETING.