Support Cloud Run services as an execution environment for agents

Open
#6,637 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
google-cloud, python
Domain
backend, cloud

Research direction

Start by reading services/hackbot-api/app/jobs.py, including its use of google.cloud.run_v2.JobsClient, ExecutionsClient, and the hardcoded "agent" container name. Trace how agents are currently launched and where the execution backend boundary belongs. Done means the existing Cloud Run Jobs path is behind an abstraction and agents can also use a Cloud Run Services backend for resident or fast-response workloads.

Written by the indexing model from the issue text.

Description

hackbot

services/hackbot-api/app/jobs.py is hard-wired to Cloud Run Jobs (google.cloud.run_v2.JobsClient/ExecutionsClient, with a hardcoded "agent" container name), and there is no execution-backend abstraction. Introduce one, then add a Cloud Run Services backend for agents that need to stay resident or respond quickly rather than run to completion.

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.