harness / harness/backstage-plugins
[Bug]: Re-run functionality doesn't take updated input set
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behaviour
When an input set is updated for a particular pipeline for eg they add a run time variable,On re-run it should throw an error (as the previous execution won't have that input).On Harness it is handled on the UI
For eg (testvariable is the updated input)
Actual behaviour
So currently on re-run on updated input set ,it will pass null for runtime variables which is not ideal.
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
The issue mentions no files or tests. Start by tracing the plugin's re-run functionality and how it handles updated pipeline input sets, then reproduce the case where a runtime variable was added. Done means re-running detects the missing input and reports an error instead of passing null.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100