Skip to content

Repository files navigation

Terraform / OpenTofu provider for Yeti

Manage a Yeti softswitch through its admin JSON:API (/api/rest/admin).

Usage

terraform {
  required_providers {
    yeti = {
      source  = "yeti-switch/yeti"
      version = "~> 0.1"
    }
  }
}

provider "yeti" {
  endpoint = "https://yeti.example.org"
  username = var.yeti_username
  password = var.yeti_password
}

resource "yeti_contractor" "acme" {
  name   = "ACME Telecom"
  vendor = true
}

With OpenTofu, replace the terraform {} block's source registry resolution by configuring the OpenTofu registry — the HCL above is otherwise identical.

Provider configuration

Attribute Env var Description
endpoint YETI_ENDPOINT Yeti base URL (no path), e.g. https://yeti.example.org
username YETI_USERNAME Admin username (minted into a JWT via /auth)
password YETI_PASSWORD Admin password
token YETI_TOKEN Pre-issued JWT; takes precedence over username/password
insecure YETI_INSECURE Set to true to skip TLS verification

Authentication uses POST /api/rest/admin/auth to exchange credentials for a JWT, then sends it as a Bearer token. JWT lifetime is governed by the server's api.token_lifetime setting.

About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages