VSD - User defined YAML config overrides built-in YAML configuration

Background

In the VSD MvC we provided the ability to customize the dashboard using a custom YAML configuration. At that point, there was only 1 possible Value Streams Dashboard, with the move to adopting the shared analytics framework for VSD, user's can now define their own dashboard configurations.

Problem

image

The original implementation relied on overriding the built in dashboard structure with the configuration a user provides. This was partially carried over into shared analytics, causing 2 dashboards to appear that both use a similar structure.

Proposal

We should:

  • Ensure the "default" built in VSD configuration is always available unmodified (labelled Created by GitLab)
  • Ensure YAML configurations appear as a separate dashboard reflecting the user's preferences

Note

  • Shared analytics dashboards uses the YAML file name as the URL slug for a dashboard, we might need to prevent user's from creating a custom dashboard that is titled "value_streams_dashboard.{yaml|yml}`