maintainx-multi-env-setup
Configure multiple MaintainX environments (dev, staging, production). Use when setting up environment-specific configurations, managing multiple MaintainX accounts, or implementing environment promotion. Trigger with phrases like "maintainx environments", "maintainx staging", "maintainx dev prod", "maintainx multi-environment", "maintainx config".
What this skill does
# MaintainX Multi-Environment Setup
## Overview
Configure and manage multiple MaintainX environments for development, staging, and production with proper secret management and client isolation.
## Prerequisites
- Separate MaintainX accounts or organizations for each environment
- Secret management solution (environment variables, GCP Secret Manager, or AWS SSM)
- Node.js 18+
## Instructions
### Step 1: Environment Configuration
```typescript
// src/config/environments.ts
interface MaintainXEnvConfig {
apiKey: string;
orgId?: string;
baseUrl: string;
label: string;
rateLimit: { requestsPerSecond: number };
}
type Environment = 'development' | 'staging' | 'production';
function getConfig(env: Environment): MaintainXEnvConfig {
const configs: Record<Environment, () => MaintainXEnvConfig> = {
development: () => ({
apiKey: process.env.MAINTAINX_API_KEY_DEV!,
orgId: process.env.MAINTAINX_ORG_ID_DEV,
baseUrl: 'https://api.getmaintainx.com/v1',
label: 'Development',
rateLimit: { requestsPerSecond: 5 },
}),
staging: () => ({
apiKey: process.env.MAINTAINX_API_KEY_STAGING!,
orgId: process.env.MAINTAINX_ORG_ID_STAGING,
baseUrl: 'https://api.getmaintainx.com/v1',
label: 'Staging',
rateLimit: { requestsPerSecond: 10 },
}),
production: () => ({
apiKey: process.env.MAINTAINX_API_KEY_PROD!,
orgId: process.env.MAINTAINX_ORG_ID_PROD,
baseUrl: 'https://api.getmaintainx.com/v1',
label: 'Production',
rateLimit: { requestsPerSecond: 20 },
}),
};
const config = configs[env]();
if (!config.apiKey) {
throw new Error(`Missing API key for ${env} environment`);
}
return config;
}
export const currentEnv = (process.env.MAINTAINX_ENV || 'development') as Environment;
export const config = getConfig(currentEnv);
```
### Step 2: Client Factory
```typescript
// src/client-factory.ts
import { MaintainXClient } from './client';
const clients = new Map<string, MaintainXClient>();
export function getClient(env?: Environment): MaintainXClient {
const targetEnv = env || currentEnv;
if (!clients.has(targetEnv)) {
const cfg = getConfig(targetEnv);
clients.set(targetEnv, new MaintainXClient(cfg.apiKey, cfg.orgId));
}
return clients.get(targetEnv)!;
}
// Usage
const devClient = getClient('development');
const prodClient = getClient('production');
```
### Step 3: Environment Files
```bash
# .env.development
MAINTAINX_ENV=development
MAINTAINX_API_KEY_DEV=dev-key-here
MAINTAINX_ORG_ID_DEV=org-dev-123
# .env.staging
MAINTAINX_ENV=staging
MAINTAINX_API_KEY_STAGING=staging-key-here
MAINTAINX_ORG_ID_STAGING=org-staging-456
# .env.production
MAINTAINX_ENV=production
MAINTAINX_API_KEY_PROD=prod-key-here
MAINTAINX_ORG_ID_PROD=org-prod-789
```
```bash
# .gitignore — never commit real keys
.env
.env.development
.env.staging
.env.production
```
### Step 4: GCP Secret Manager Integration
```typescript
// src/config/secrets.ts
import { SecretManagerServiceClient } from '@google-cloud/secret-manager';
const secretClient = new SecretManagerServiceClient();
async function getSecret(name: string): Promise<string> {
const [version] = await secretClient.accessSecretVersion({
name: `projects/your-project/secrets/${name}/versions/latest`,
});
return version.payload!.data!.toString();
}
async function loadProductionConfig(): Promise<MaintainXEnvConfig> {
return {
apiKey: await getSecret('maintainx-api-key-prod'),
orgId: await getSecret('maintainx-org-id-prod'),
baseUrl: 'https://api.getmaintainx.com/v1',
label: 'Production',
rateLimit: { requestsPerSecond: 20 },
};
}
```
### Step 5: Validation Script
```typescript
// scripts/validate-environments.ts
import 'dotenv/config';
const envs: Environment[] = ['development', 'staging', 'production'];
async function validateAll() {
for (const env of envs) {
try {
const cfg = getConfig(env);
const client = new MaintainXClient(cfg.apiKey, cfg.orgId);
const { data } = await client.getUsers({ limit: 1 });
console.log(`${cfg.label}: OK (${data.users.length} user(s) found)`);
} catch (err: any) {
console.error(`${env}: FAILED - ${err.message}`);
}
}
}
validateAll();
```
```bash
# Run validation
npx tsx scripts/validate-environments.ts
# Development: OK (1 user(s) found)
# Staging: OK (1 user(s) found)
# Production: OK (1 user(s) found)
```
## Output
- Environment-specific configuration with type-safe config loader
- Client factory producing isolated clients per environment
- `.env.*` files with `.gitignore` protection
- GCP Secret Manager integration for production secrets
- Validation script to verify all environment credentials
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Missing API key | Environment variable not set | Check `.env.*` file for target environment |
| Wrong environment data | Using prod key in dev | Verify `MAINTAINX_ENV` is set correctly |
| Secret Manager 403 | Missing IAM permissions | Grant `secretmanager.secretAccessor` role |
| Config mismatch after deploy | Old secrets cached | Clear client cache, reload secrets |
## Resources
- MaintainX API Reference
- [12-Factor App: Config](https://12factor.net/config)
- [GCP Secret Manager](https://cloud.google.com/secret-manager/docs)
## Next Steps
For observability setup, see `maintainx-observability`.
## Examples
**GitHub Actions with per-environment secrets**:
```yaml
# .github/workflows/deploy.yml
jobs:
deploy:
runs-on: ubuntu-latest
environment: ${{ github.ref == 'refs/heads/main' && 'production' || 'staging' }}
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- run: npm run validate-env
env:
MAINTAINX_ENV: ${{ vars.MAINTAINX_ENV }}
MAINTAINX_API_KEY_PROD: ${{ secrets.MAINTAINX_API_KEY }}
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.