You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just realized 35deaab moved allow blocks from metadata to config.
Could this result in previously secured instances opening up when the upgrade is applied? If so, it would be better to fail hard (like we used to with plugin configuration prior to #2248).
The text was updated successfully, but these errors were encountered:
It should treat them as if they were in config. I've decided to support that for everything - metadata gets silently upgraded to config, rather than breaking things for people.
simonw
changed the title
Should Datasette fail if allow blocks are in metadata?
Treat allow blocks in metadata as if they were in config
Feb 5, 2024
Closes#2243
* Changelog for jinja2_environment_from_request and plugin_hook_slots
* track_event() in changelog
* Remove Using YAML for metadata section - no longer necessary now we show YAML and JSON examples everywhere.
* Configuration via the command-line section - #2252
* JavaScript plugins in release notes, refs #2052
* /-/config in changelog, refs #2254
Refs #2052, #2156, #2243, #2247, #2249, #2252, #2254
I just realized 35deaab moved allow blocks from metadata to config.
Could this result in previously secured instances opening up when the upgrade is applied? If so, it would be better to fail hard (like we used to with plugin configuration prior to #2248).
The text was updated successfully, but these errors were encountered: