You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most fields in config are the same in all env (prod and preprod). These fields should live in a single file, and not be repeated in all files (config.preprod.json, config.prod.json), so that there is a single source of truth, and they always stay in sync.
Why would you like to do it?
To avoid having differences appear by mistake between prod and preprod configs.
How would you like to achieve it?
Can we add one config on top of the other, and overwrite some of the fields ?
Or apply configs from two files : one for the common fields, one for the special fields for this env.
Or store a diff of the two files, and apply the diff in the package script.
Or merge the two json files in the package script.
Ask element if they have solved this problem.
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
un fichier config.base.json et des config.json qui contiennent que les champs à modifier
utiliser le systeme existant de chargement de conf, et avoir un config.json pour tout le monde, plus un config.localhost.json ou autre qui est reconnu par le loader en fonction du nom de domaine
Your use case
What would you like to do?
Most fields in config are the same in all env (prod and preprod). These fields should live in a single file, and not be repeated in all files (config.preprod.json, config.prod.json), so that there is a single source of truth, and they always stay in sync.
Why would you like to do it?
To avoid having differences appear by mistake between prod and preprod configs.
How would you like to achieve it?
Can we add one config on top of the other, and overwrite some of the fields ?
Or apply configs from two files : one for the common fields, one for the special fields for this env.
Or store a diff of the two files, and apply the diff in the package script.
Or merge the two json files in the package script.
Ask element if they have solved this problem.
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: