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).
22 lines
1.1 KiB
JSON
22 lines
1.1 KiB
JSON
{
|
|
"_comment_signal": "Use SIGTERM (which the app already handles) instead of nodemon's default SIGUSR2. This ensures every restart triggers the graceful shutdown() path in index.js, which calls framework.stop() and webex.internal.device.unregister(). Without this, each save would leak a WDM device registration and you'd eventually hit Cisco's per-bot device cap with 'Forbidden: User has excessive device registrations' on startup.",
|
|
"_comment_delay": "Wait 1s after a file change before restarting — collapses bursts of saves (e.g. format-on-save touching multiple files) into a single restart.",
|
|
"_comment_signal_timeout_workaround": "nodemon's `kill` setting controls how long it waits between sending the configured signal and SIGKILL'ing the app. 5s gives framework.stop()'s DELETE /wdm/api/v1/devices call enough time to complete on a typical RTT to Cisco.",
|
|
"signal": "SIGTERM",
|
|
"delay": 1000,
|
|
"kill": 5000,
|
|
"watch": [
|
|
"index.js",
|
|
"commands/",
|
|
"integrations/",
|
|
"utils/"
|
|
],
|
|
"ext": "js,json",
|
|
"ignore": [
|
|
"node_modules/",
|
|
"public/",
|
|
"logs/",
|
|
"tokens/",
|
|
"*.test.js"
|
|
]
|
|
}
|