How haricrazy1432-bot/itops works
ITOPS handles software-install requests: users submit requests through an HTTP endpoint, which creates a ServiceNow ticket and records request details locally. Supervisors use bot commands to approve or reject tickets, or trigger Rundeck installation; installation completion updates both the ServiceNow ticket and local request status. The graph separates intake, supervisor actions, persistence, and the ServiceNow and Rundeck integrations. Relationships are limited to calls shown in the excerpts; the README provides no additional capability details.
Main entry points: app.py Bot commands · server.py ServiceNow API · servicenow_client.py ServiceNow client · rundeck_client.py Rundeck client
Components 10
Request intake
- Request intake
bot/app.py
Supervisor operations
- Bot commands
bot/app.py
Request records
- Request database
bot/software.db
External integrations
- ServiceNow API
mcp/server.py - ServiceNow client
mcp/servicenow_client.py - ServiceNow
- Rundeck client
bot/rundeck_client.py - Rundeck
Other components
- Software requester
- Supervisor
Connections 10
- Software requester → Request intake: submits request
bot/app.py - Supervisor → Bot commands: sends commands
bot/app.py - Request intake → ServiceNow API: creates ticket
bot/app.py - Request intake → Request database: stores request
bot/app.py - Bot commands → Request database: reads and updates
bot/app.py - Bot commands → ServiceNow API: updates ticket
bot/app.py - Bot commands → Rundeck client: triggers and polls
bot/app.py - ServiceNow API → ServiceNow client: dispatches ticket calls
mcp/server.py - ServiceNow client → ServiceNow: creates and updates
mcp/servicenow_client.py - Rundeck client → Rundeck: runs and checks jobs
bot/rundeck_client.py