rossoctl / rossoctl/rossoctl

feature: Allow updating build options in the UI after import failure

Open
#1,002 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
302
Forks
107
Avg merge
1d 16h
Merged PRs (30d)
41

Description

Feature Description

When I import an agent and I made a mistake in the configuration (e.g. missing env variable), the build fails.

Today, there is only the option to rerun the build, but there is no way to correct the parameters, forcing me to reaply all the configuration.

Proposed Solution

Allow editing for build params after failures and start a new build.

Want to contribute?
  • I would like to work on this issue.
Additional Context
Image

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.

Research direction

Start by locating the UI flow for imported agents whose builds fail and the handling of build parameters and retry actions. Trace how failed-build parameters are displayed and persisted, then verify that users can edit them and start a new build without reapplying the full configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.