Project

General

Profile

Actions

Bug #22830

open

Ansible playbooks should respect config.default.yml

Added by Brett Smith 11 months ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Deployment
Target version:
-
Story points:
-

Description

The way Arvados is supposed to be configured is services start by reading config.default.yml and then merge in the cluster config.yml. config.yml is expected to only have settings that the administrator has actually changed.

Our Ansible playbooks don't really respect this. If they need a value from Arvados configuration, they usually assume they can find it in the administrator's config.yml. There are some hard-coded defaults in the code but this approach isn't scalable and risks drifting away from config.default.yml.

Plan and implement a way for all of our Ansible playbooks to initialize the arvados_config fact with values from config.default.yml.


Related issues 2 (2 open0 closed)

Related to Arvados - Feature #22862: Ansible playbooks should validate Arvados config before useNewActions
Related to Arvados Epics - Idea #18337: Easier install using AnsibleIn Progress01/01/202508/31/2025Actions
Actions #1

Updated by Peter Amstutz 10 months ago

  • Target version set to Development 2025-06-25
Actions #2

Updated by Peter Amstutz 10 months ago

  • Related to Feature #22862: Ansible playbooks should validate Arvados config before use added
Actions #3

Updated by Peter Amstutz 10 months ago

  • Target version changed from Development 2025-06-25 to Development 2025-07-09
Actions #5

Updated by Brett Smith 9 months ago

  • Target version deleted (Development 2025-07-09)
Actions #6

Updated by Brett Smith 9 months ago

  • Related to Idea #18337: Easier install using Ansible added
Actions

Also available in: Atom PDF