Making gdk reconfigure work well without removing important configuration
Right now many of us avoid running gdk reconfigure
since it blows away important configuration, such as OAuth2, LDAP, and Geo-specific settings.
We need a better way to pick up new changes in gitlab.yml
without losing that information.
I propose:
- We have a separate YAML file (e.g.
gitlab.yml.development
) that defines attributes we want persistent -
gdk reconfigure
can loadgitlab.yml.example
and attempt to merge in the changes from that YAML file - Upon success, just write the file out as
gitlab.yml
. If there are inconsistencies with the key/value structure, abort with an error.
Thoughts?