linear-multi-env-setup

name	linear-multi-env-setup
description	Configure Linear across development, staging, and production environments. Use when setting up per-environment API keys, secret management, or environment-specific Linear configurations. Trigger: "linear environments", "linear staging", "linear dev prod", "linear environment setup", "multi-environment linear".
allowed-tools	Read, Write, Edit, Bash(vault:*), Bash(gcloud:*), Bash(aws:*)
version	1.12.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","linear","deployment","api"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Linear Multi-Environment Setup

Overview

Configure Linear integrations across dev, staging, and production with isolated API keys, secret management, environment guards, and per-environment webhook routing. Use separate Linear workspaces or at minimum separate API keys per environment.

Prerequisites

• Separate Linear API keys per environment (dev, staging, prod)
• Secret management (Vault, AWS Secrets Manager, GCP Secret Manager)
• CI/CD pipeline with environment support
• Node.js 18+

Instructions

Step 1: Environment Configuration

// src/config/linear.ts
import { LinearClient } from "@linear/sdk";

interface LinearEnvConfig {
  apiKey: string;
  webhookSecret: string;
  defaultTeamKey: string;
  enableWebhooks: boolean;
  enableDebugLogging: boolean;
  cacheEnabled: boolean;
}

type Environment = "development" | "staging" | "production" | "test";

function getEnvironment(): Environment {
  const env = process.env.NODE_ENV ?? "development";
  if (!["development", "staging", "production", "test"].includes(env)) {
    throw  ();
  }
   env  ;
}

  (): <> {
   env = ();

  
   (env ===  || env === ) {
     {
      :  (),
      :  (),
      : process.. ?? ,
      : ,
      : env === ,
      : ,
    };
  }

  
   {
    : process.. ?? ,
    : process.. ?? ,
    : process.. ?? ,
    : , 
    : ,
    : ,
  };
}