[ckan-dev] pylons.app_globals vs pylons.config

[Sean Hammond]

> 8) do some validation of options at ckan start-up - including that it has
> documentation.

Yeah this would really help a lot.

But even if we implement a CKAN options system in app_globals of
wherever that has this sort of validation, how can we prevent code
from just accessing some undocumented option via pylons.config directly?
If we really want it to work we might have to monkey-patch something