jmcqueen
351f89a9a4
Multi-integration Webex chat/HTTP bot that unifies phone, AV, and network status for retail store support. Consolidates data from Webex Calling, Meraki, Workspace ONE (MDM), Atlas AMP, RED digital signage, and OptiSigns into rich per-store status commands. Key surfaces: - /phonestatus, /avstatus — per-store phone & AV device reports with clickable Meraki deep-links and per-port detail. - /webexhost — check/assign Webex Meetings host licenses via the Service App; adaptive-card confirmation flow, HTTP-API-gated. - /offboarduser — full Webex Admin offboarding (auth revoke, device wipe, license removal); adaptive-card confirmation. - /jirapoll — on-demand trigger for the hourly Jira poller. - /bulkavstatuscsv — bulk store CSV export with concurrency limits. Automation: - Hourly Jira poller (node-cron) with an X.AI (Grok) ticket classifier that categorizes unassigned tickets as phone/av/skip, extracts store numbers from free-text, and enriches Jira with the same detailed markdown the chat commands emit (converted to Jira ADF, preserves bold + Meraki links). Idempotent via a `bot-enriched` Jira label. Architecture: - Node.js 20+, ESM, Express 5, webex-node-bot-framework. - Layered integrations (integrations/*), services (services/*), commands (commands/*), utils (utils/*). - Shared markdown renderers (services/renderers/*) feed both chat handlers and the Jira poller so the two surfaces stay in sync. - Hand-rolled markdown-to-ADF converter (utils/markdownToAdf.js) — no new npm dependency. - Node built-in test runner (`node --test tests/*.test.js`), 30 tests covering the converter, renderers, and poller ADF assembly. Docker + docker-compose deployment. Config via .env (see .env.example for the full option surface).
50 lines
1.9 KiB
JavaScript
50 lines
1.9 KiB
JavaScript
// src/commands/avStatus.js
|
||
//
|
||
// Chat + HTTP entry point for /avstatus. The heavy rendering lives in
|
||
// services/renderers/avStatusRenderer.js so the Jira poller can emit
|
||
// the same markdown (see services/jiraPollerService.js). This handler
|
||
// stays thin: parse args, call the collector, hand data to the renderer,
|
||
// respond.
|
||
|
||
import { collectDeviceStatus } from '../services/deviceService.js';
|
||
import { renderAvStatusMarkdown } from '../services/renderers/avStatusRenderer.js';
|
||
import { logger } from '../utils/logger.js';
|
||
|
||
export async function handleAvStatus(bot, trigger) {
|
||
logger('device:status', 'Handler entered', 'debug');
|
||
|
||
const query = trigger.query || {};
|
||
const args = trigger.args || [];
|
||
|
||
let storeNum = args[0]?.trim() || query.storeNum || query.store || query.s;
|
||
|
||
const isDetailed =
|
||
(args[1]?.toLowerCase() === 'detailed') ||
|
||
(query.mode === 'detailed') ||
|
||
(query.detailed === 'true' || query.detailed === true);
|
||
|
||
if (!storeNum || !/^\d{2,4}$/.test(storeNum)) {
|
||
const errorMsg = 'Please provide a 2–4 digit store number.\n' +
|
||
'Example: `/avstatus 782` (or `detailed` / `?detailed=true` for more; includes Meraki deep links) or `https://.../avstatus?storeNum=782`';
|
||
await bot.say('markdown', errorMsg);
|
||
return;
|
||
}
|
||
|
||
logger('device:status', `Collecting AV device status for store ${storeNum} in detailed mode`, 'debug');
|
||
|
||
try {
|
||
const data = await collectDeviceStatus(storeNum);
|
||
const reply = renderAvStatusMarkdown(data, {
|
||
storeNum,
|
||
detailed: isDetailed,
|
||
footer: true,
|
||
});
|
||
await bot.say('markdown', reply);
|
||
|
||
const mdmDevices = data.mdm?.data || [];
|
||
logger('device:status', `Rendered detailed view for ${mdmDevices.length} MDM devices`);
|
||
} catch (err) {
|
||
logger('device:status', `Error: ${err.message}`, 'error');
|
||
await bot.say('markdown', `❌ Error collecting device status: ${err.message}`);
|
||
}
|
||
}
|