#6422 feat: Add visibility of setting values across all stores to the CLI config list command Issue created by kgpayne Per this comment, one of the side-effects of #6116 is that we may in certain circumstances duplicate configuration where previously we would have updated/overwritten values: # First place a regular setting in a low-priority store... meltano config tap-gitlab set --store=db api_url 'https://gitlab.com/old_value' # ...then try to update it via the auto store. meltano config tap-gitlab set api_url 'https://gitlab.com/new_value' # Previously this would have updated 'https://gitlab.com/old_value' to 'https://gitlab.com/new_value' in the system db, # because we used current value source to override other valid stores. # As of this change, we will in stead get two values for the setting 'api_url' in two different stores (system db and the default meltano.yml). To make it easier to debug these cases, we could add additional visibility of setting values to the existing

meltano config <plugin> list

command. An example output might be something like: ❯ meltano config tap-github list access_token [env: TAP_GITHUB_ACCESS_TOKEN] current value: 'my_value' (from the TAP_GITHUB_ACCESS_TOKEN variable in

.env

) overriden value(s):

my_sub_value

(from the system database) ... meltano/meltano