Design decision - should configuration be exposed at /-/config ?

[simonw]

This made me think. That {"$env": "ENV_VAR"} hack was introduced back here:

• Mechanism for secrets in plugin configuration #538

The problem it was solving was that metadata was visible to everyone with access to the instance at /-/metadata but plugins clearly needed a way to set secret settings.

Now that this stuff is moving to config, we have some decisions to make:

1. Add /-/config to let people see the configuration of their instance, and keep the $env trick for secret settings.
2. Say all configuration aside from metadata is secret and make $env optional or ditch it entirely.
3. Allow plugins to announce which of their configuration options are secret so we can automatically redact them from /-/config

I've found /-/metadata extraordinarily useful as a user of Datasette - it really helps me understand exactly what's going on if I run into any problems with a plugin, if I can quickly check what the settings look like.

So I'm leaning towards option 1 or 3.

Originally posted by @simonw in #2183 (comment)

Also refs:

• Proposal: Combine settings, metadata, static, etc. into a single datasette.yaml File #2093