Allow adding a new Hackbot agent without modifying or redeploying hackbot-api

Open
#6,644 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend-api-design

Research direction

Start by reading services/hackbot-api/app/schemas.py and the agent hackbot.toml/AgentInputs references in the issue. Trace how endpoint wiring and input schemas are currently duplicated, then define what self-description must expose for hackbot-api to discover an agent. Done means a new agent can be added without changing hackbot-api source or redeploying the service.

Written by the indexing model from the issue text.

Description

hackbot

Adding a new agent currently requires code changes in hackbot-api (endpoint wiring and input schemas duplicated in services/hackbot-api/app/schemas.py) plus a redeploy of the service. Make agent registration self-describing, for example derived from each agent's hackbot.toml/AgentInputs, so hackbot-api can pick up new agents without a source change or redeploy.

Dominant language
Python
Stars
570
Forks
351
Avg merge
2d 11h
Merged PRs (30d)
61

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/bugbug

All issues in mozilla/bugbug

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.