feat: set arbitrary plugin config value at cli

[dbluhm]

Doing a bit of spit balling.

We previously addressed the need for supplying configuration to plugins with the --plugin-config flag to load a yaml file into settings for use by plugins. We've found this feature to be quite helpful, especially in the case of loading multiple plugins (i.e. resolvers) that each require their own configuration. However, we have also found that it would be handy to be able to set or modify these values from the command line. So instead of having to modify the plugin_config.yml you're using to load the universal resolver plugin to point it to a different resolver instance, we could have a command line argument like the following:

--plugin-config-value http_uniresolver.endpoint=http://localhost:3000

Or perhaps a short form of:

-o http_uniresolver.endpoint=http://localhost:3000

With such a command line argument, we propose that dotted key values act as a shorthand for nesting values. For example, a.b.c.d=value becomes {"a": {"b": {"c": {"d": "value"}}}}. We also propose that the value be loaded as yaml to avoid parsing ourselves while still allowing us to express values more complicated than just strings and numbers.

Open to thoughts 🙂

[codecov-commenter]

Codecov Report

Merging #1347 (4f9b732) into main (1f8eeb0) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1347   +/-   ##
=======================================
  Coverage   95.43%   95.43%           
=======================================
  Files         476      476           
  Lines       28977    28988   +11     
=======================================
+ Hits        27653    27664   +11     
  Misses       1324     1324           

[andrewwhitehead]

Seems reasonable to me, can you write something like --plugin-config-value "a.b.c=[one,two]" ?

[dbluhm]

Yep, [one, two], {inline: yaml_dict}, true, etc. all get parsed into the expected values