dev/core#1460 - Apply different dispatch policies during main and finish phases
authorTim Otten <totten@civicrm.org>
Mon, 20 Apr 2020 22:34:41 +0000 (15:34 -0700)
committerTim Otten <totten@civicrm.org>
Tue, 21 Apr 2020 05:59:13 +0000 (22:59 -0700)
commit29b6189cb56160781f37b840989968e0331acaed
treee82f033b8f24ff7bf7afe5bd5a029f68a3e40d60
parentecb0ae5d0d607a53da2037f7fc618c38e23b81db
dev/core#1460 - Apply different dispatch policies during main and finish phases

This is the culmination of the preceding commits: when running upgrades,
we don't just apply one brittle whitelist throughtout the process. Instead:

- Apply a very restrictive dispatch policy while executing incremental DB updates,
  preventing interference from unexpected callpaths.
- Apply a very permissive dispatch policy while executing the final cleanup/reset,
  allowing more data-structures to rehydrate correctly.
CRM/Upgrade/DispatchPolicy.php