Talks about #2628144: Ensure that ConfigImport is taking place against the same code base → making config import more reliable. There is some contention because it reduces some of the abilities of developers to do what they please. This issue is going to do something simpler. Ensure that when running configuration import there are no outstanding database updates to run.
Add validator to ensure that no outstanding updates need running.
Additional configuration import validation messages
None
For kernel tests we have added \Drupal\KernelTests\KernelTestBase::installUpdateRegistryState() to set the state for modules so that config imports are easy to test.
None
Config imports are prevented if there are outstanding database updates → . In order to import Configuration, all available updates must have been run. This change helps users follow best practices around configuration management, drupal updates and deployments → .
Needs work
9.5
Last updated
There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Ah no! you misunderstood!
Drupal does not have a UI to run deploy hooks (yet). But deploy hooks are a thing already for a while and work in production with the stable drush version since two years.
So since you are using drush this is already available to you.
Deploy hooks work the same way as post update hooks.