Skip to content

Remove unused jira-escalation command and SlackClient bot integration#276

Draft
amp-rh wants to merge 1 commit into
mainfrom
remove-dead-slack-escalation-code
Draft

Remove unused jira-escalation command and SlackClient bot integration#276
amp-rh wants to merge 1 commit into
mainfrom
remove-dead-slack-escalation-code

Conversation

@amp-rh
Copy link
Copy Markdown
Collaborator

@amp-rh amp-rh commented Apr 22, 2026

Summary

Removes dead code that was never wired up to any CI job or Prow step:

  • src/commands/jira_escalation.py — CLI command
  • src/escalation/jira_escalation.py — escalation logic
  • src/objects/slack_base.py — SlackClient bot token integration
  • Associated tests

Why

The jira-escalation command and SlackClient (bot token based) existed in the codebase but were never referenced in the step registry or any Prow job config. SLACK_BOT_TOKEN was never injected anywhere in CI.

Slack notifications for the report command are handled via incoming webhook in #274, which requires no bot token or SDK.

Test plan

  • Unit tests pass (uv run pytest tests/unittests/)
  • firewatch --help no longer lists jira-escalation

Neither the jira-escalation CLI command nor the SlackClient bot token
integration were wired up to any CI job or Prow step. Removing the dead
code: jira_escalation command, escalation logic, SlackClient class, and
associated tests.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 22, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant