cloud-bulldozer / cloud-bulldozer/performance-dashboards

Make performance-dashboards disconnected friendly

Open
#32 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Jsonnet
Stars
20
Forks
46
PR merge metrics
No merged PRs in 30d

Description

I am unsure if there was a specific design reason to put git cloning as a script into the [syncer container image](https://github.com/cloud-bulldozer/performance-dashboards/blob/master/dittybopper/templates/dittybopper.yaml.template#L69) however this makes performance-dashboards incompatible with environments that can not reach github.com. Could we put the templates directly into the container image or git clone but fallback to templates in the image instead of always trying to pull down the latest master branch?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with dittybopper/templates/dittybopper.yaml.template at the syncer container image definition and trace the script that clones templates from GitHub. Check how the image behaves when github.com is unreachable and determine how bundled templates or a fallback should be selected. Done means performance-dashboards can start in a disconnected environment without requiring access to GitHub.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, git, yaml
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.