harness / harness/backstage-plugins
[Feat]: Allow support for harness.io/pipelines annotations without the keys
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
🔖 Feature description
Currently the harness.io/pipelines annotations expects an array of key value pairs like this
metadata:
annotations:
harness.io/pipelines: |
ci: ci_pipeline_link
cd: cd_pipeline_link
key1: url1
However it should also be possible to skip these keys here. If the keys are missing, then the pipeline name can be used as the keys in the dropdown list.
metadata:
annotations:
harness.io/pipelines: |
ci_pipeline_link
cd_pipeline_link
url1
or simply
metadata:
annotations:
harness.io/pipelines: pipeline_link
🎤 Context
✌️ Possible Implementation
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 at the linked annotation-handling code in plugins/harness-ci-cd/src/components/ExecutionList/ExecutionList.tsx around lines 291–296. Trace how harness.io/pipelines values are parsed and displayed, then support both keyed and keyless forms, using pipeline names as dropdown keys when keys are absent. Done means all three examples render with usable labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100