Enhancement: Allow to query workflow runs against multiple repositories at once
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the GitHub API workflow-runs request described in the issue and inspect where repository selection becomes a query; the payload names no files or tests. Done means a dashboard can select multiple repositories and receive combined workflow-run results while retaining the organization, workflow filename, and optional branch inputs.
Written by the indexing model from the issue text.
Description
My goal is to have a centralised (one per a whole Github ORG) dashboard with all workflow runs in the whole organisation.
In order to query workflow runs the following parameters are needed:
- Github ORG name - this is a static value basically
- repository name - it's easy to get all repositories across the ORG using a separate query
- workflow filename - it is problematic to get list of workflow filenames dynamically, however most of my workflow filenames are the same, so I can work with that and hardcode this value
- (branch name is optional)
Based on that we have all elements we need, however a query to Github API can use only one parameter, so we can query a single org-repo-filename combination at once.
So I was thinking that maybe the plugin can detect if multiple repository names are provided and break the query into multiple sub-queries in order to return the results? This is more or less how Prometheus datasource plugin works when multiple values are selected from the dropdown boxes (eg. query for CPU usage in VM1, VM2, VM3).
I'm happy to discuss alternative solutions as well. Many thanks in advance!
- Dominant language
- Go
- Stars
- 311
- Forks
- 72
- Avg merge
- 10d 1h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from grafana/github-datasource
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
grafana/github-datasource#796 · 2 comments ·
-
Bug: Workflow_Runs query type consistently returns 0 rows when same URL+token directly returns dataOpen
Difficulty 4/5 3-5 days Newbie friendliness 52/100
grafana/github-datasource#774 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
grafana/github-datasource#760 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
grafana/github-datasource#528 · 4 comments ·
-
Dependency DashboardOpen
Difficulty 4/5 3-5 days Newbie friendliness 12/100
grafana/github-datasource#523 ·
All issues in grafana/github-datasource
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
prime-radiant-inc/evener#3726 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
temporalio/deputy#400 ·
Maintainers usually reply within 1 day
-
[BUG] Async engine endpoint-label relationship counts include pending relationships of every typeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
status/0-needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day