harness / harness/backstage-plugins
[Bug]: harness.io/project-url has to end with / or the plugin doesn't work
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
If I set a harness.io/project-url like https://app.harness.io/ng/#/account/accountID/cd/orgs/orgId/projects/projectId it should work.
Actual behavior
Plugin says no pipelines found.
Possible Implementation
This regex should be updated. It expects a trailing /.
Either we append a trailing / when parsing the annotation ourselves in code. Or we update the regex to ignore the /.
cc @SarvJ1 @sarthakkasat @Debanitrkl @sandeepa-kv-jois
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 in plugins/harness-ci-cd/src/components/ExecutionList/useProjectSlugEntity.tsx, at the regex linked in the issue. Check how it parses the harness.io/project-url annotation, then verify that a URL without a trailing slash produces the project slug and does not result in “no pipelines found.”
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100