Closed
Milestone
expired on Dec 1, 2023
Improved config.json handling when fetched via alternative channels
When loading config.json
via alternative transports, if config.json
is broken but the original website is not available, a LibResilient-enabled site might end up in a broken state
LibResilient should verify that a newly loaded config is valid broken (say, by deploying the new
configuration and attempting to load the config.json
file it just loaded), and reverting to the
previous, clearly working config otherwise.
Plan
- test possible failure modes of
config.json
loaded via alternative transports - improve handling of broken/problematic
config.json
- consider implementing deep plugin check
- update documentation