Cells gdk.yml management
Overview
We want the main gdk.yml as single source of truth and let GDK update cells' gdk.ymls
Below, I have to customize cell-1's gdk.yml, :
Click to expand
---
asdf:
opt_out: true
cells:
port_offset: 12000
gitlab_http_router:
enabled: false
hostname: gdk.test
vite:
enabled: true
webpack:
enabled: false
gitlab:
rails:
session_store:
session_cookie_token_prefix: abcd
It will be ideal to move this to primary gdk.yml instead:
cells:
enabled: true
instance_count: 1
gdk_configs: # For all cells
vite:
enabled: true
webpack:
enabled: false
instances:
- name: cell_1
config: # Only for cell_1
gitlab:
rails:
session_store:
session_cookie_token_prefix: abcd
Implementation Details
- We need the ability to configure arbitrary settings for all secondary cells
- We need the ability to configure arbitrary settings for individual secondary cells
Impacted categories
The following categories relate to this issue:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Steps to replicate (optional)
Proposal (optional)
Make it so that arbitary settings is propagated to all cell's gdk.yml
Environment (optional)
- Operating system name:
<!-- output of `uname -a` command --> - Architecture:
<!-- output of `arch` command --> - The contents of your
gdk.yml(if any) - Ruby version:
<!-- output of `ruby --version` command --> - GDK version:
<!-- output of `git rev-parse --short HEAD` command -->
Edited by Peter Leitzen