harness / harness/backstage-plugins
[Feat]: Improve initial loading time for execution
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
🔖 Feature description
Currently the plugin if serviceID is configured, makes 4 API calls for it to show the executions.This happens only during the first time you load the executions.
🎤 Context
- The first API is to check for the licenses issued to the account
- As we currently take latest 5 pipelines that have been executed for the particular service,for that we need the service name
- So second API gets us the service name which we will use to filter and get latest 5 pipelines
- Third API gets us the latest 5 pipelines with that particular service name
- Fourth API gets us our executions
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
Trace the plugin's initial execution-loading flow and map the four API calls described in the issue: license checks, service-name lookup, pipeline lookup, and execution retrieval. Determine which calls can be avoided or combined while preserving the latest five service pipelines and displayed executions; done means the initial load is faster with correct results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100