菜单
Azure-native warehouse in CSA Loom — back it with a Synapse dedicated SQL pool, never a Fabric Warehouse. Call synapse-sql-client.ts + synapse-pool-arm.ts via /api/warehouse and /api/synapse. Triggers on warehouse, data warehouse, SQL endpoint, dedicated pool, T-SQL, DWU, scale warehouse.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | loom-warehouse |
| description | Azure-native warehouse in CSA Loom — back it with a Synapse dedicated SQL pool, never a Fabric Warehouse. Call synapse-sql-client.ts + synapse-pool-arm.ts via /api/warehouse and /api/synapse. Triggers on warehouse, data warehouse, SQL endpoint, dedicated pool, T-SQL, DWU, scale warehouse. |
| allowed-tools | Read, Grep, Glob, Bash |
A Loom warehouse is a Synapse dedicated SQL pool (with Serverless for
ad-hoc lakehouse queries). It is NOT a Fabric Warehouse. The backend is selected
by LOOM_WAREHOUSE_BACKEND (default = synapse); fabric is opt-in only.
apps/fiab-console/lib/azure/synapse-sql-client.ts (TDS query) and
synapse-pool-arm.ts (ARM control plane — create/pause/resume/scale DWU).
Real exported symbols:
// synapse-sql-client.ts
export interface SynapseTarget { /* server, database, ... */ }
export function getSynapseSqlSuffix(): string; // from cloud-endpoints synapseSqlSuffix()
export function dedicatedTarget(): SynapseTarget; // the dedicated pool
export function serverlessTarget(database?: string): SynapseTarget;
export function serverlessEndpoint(): string;
export interface QueryResult { /* columns, rows, rowCount, ... */ }
export interface SynapseQueryParam { /* name, value, type */ }
export async function executeQuery(target: SynapseTarget, sqlText: string, timeoutMs?: number, parameters?: SynapseQueryParam[], queryId?: string): Promise<QueryResult>;
export async function explainQuery(/* ... */): Promise<...>; // EXPLAIN plan
export async function executeQueryAsUser(/* ... */): Promise<...>; // on-behalf-of
export function cancelActiveQuery(queryId: string): boolean;
Queries authenticate with an AAD access token over TDS (mssql driver). The SQL
host suffix is synapseSqlSuffix() from cloud-endpoints.ts and the JDBC cert
host is synapseSqlJdbcHostCert() — both sovereign-correct.
UAMI-first chain; token audience is the SQL resource (getSqlSuffix()). The
UAMI must be an AAD admin / db user on the pool (granted in bicep integration).
/api/warehouse/**, /api/synapse/**. Validate session → gate on
LOOM_SYNAPSE_WORKSPACE → run real TDS via executeQuery(dedicatedTarget(), …)
→ { ok, data: { columns, rows } }. Long queries support queryId +
cancelActiveQuery().
dedicatedTarget() for warehouse T-SQL and serverlessTarget() for
ad-hoc reads over lakehouse Delta.SynapseQueryParam[] — never string-concat user input.sql.azuresynapse.net; use getSynapseSqlSuffix().UI parity: docs/fiab/parity/warehouse.md (+ synapse-* docs). Backend map row:
warehouse in .claude/rules/no-fabric-dependency.md.
Azure-native activator (Reflex) in CSA Loom — back it with an Azure Monitor scheduled-query alert (or Logic App), never Fabric Activator. Call monitor-client.ts via /api/monitor. Triggers on activator, Reflex, alert, trigger, scheduled query rule, action group, notification, data activator.
MUST-READ root skill for CSA Loom. Resolve every Azure endpoint host and AAD scope from cloud-endpoints.ts instead of hard-coding management.azure.com / kusto.windows.net / dfs.core.windows.net. Triggers on sovereign cloud, GCC, GCC-High, DoD, IL5, endpoint, hostname, ARM, scope, token audience, government cloud.
Azure-native data pipeline in CSA Loom — back it with a Synapse pipeline (or ADF), never a Fabric Data pipeline. Call synapse-dev-client.ts + adf-client.ts via /api/adf and /api/synapse. Triggers on data pipeline, copy activity, dataflow, orchestration, trigger, integration runtime, ADF, Synapse pipeline.
Azure-native Eventhouse/KQL in CSA Loom — call Azure Data Explorer (ADX) via kusto-client.ts + kusto-arm-client.ts, never Fabric RTI. Use /api/adx routes. Triggers on KQL, Eventhouse, ADX, Kusto, real-time intelligence, KQL database, KQL dashboard, ingestion mapping, materialized view, RLS.
Azure-native eventstream in CSA Loom — back it with Azure Event Hubs (+ Stream Analytics for processing), never Fabric Eventstream. Call eventhubs-client.ts + stream-analytics-client.ts via /api/eventhubs. Triggers on eventstream, Event Hubs, streaming, real-time ingestion, consumer group, Stream Analytics, capture, schema registry.
The generic CSA Loom item BFF contract. Every item type exposes /api/items/<type>/<id>/<action> returning { ok, data, error } with a real backend call and honest config gates — never mock arrays or dead handlers. Triggers on BFF route, API route, item action, session validation, config gate, response shape, NextResponse, no-vaporware.