harness / harness/backstage-plugins
[Feat]: Re-run pipeline should take inputs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
🔖 Feature description
When re-running a pipeline from the CI/CD tab, as of it is executed using the existing input sets. However, a developer might want to re-trigger using a set of new inputs. Just like Harness, there should be a way to provide those inputs in the Backstage plugin.
🎤 Context
A screenshot of the input form in Harness.

✌️ Possible Implementation
Pass additional parameters to the re-run pipeline API.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CI/CD tab's pipeline re-run action and its integration with the re-run pipeline API. Define how the Backstage plugin will collect and pass new inputs, then verify that a re-run can use those inputs instead of the existing input set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100