getConfigStorage example

/** * Returns the active configuration storage used during early install. * * This override changes the visibility so that the installer can access * config storage before the container is properly built. * * @return \Drupal\Core\Config\StorageInterface * The config storage. */
  public function getConfigStorage() {
    return parent::getConfigStorage();
  }

  /** * {@inheritdoc} */
  public function getInstallProfile() {
    global $install_state;
    if ($install_state && empty($install_state['installation_finished'])) {
      // If the profile has been selected return it.       if (isset($install_state['parameters']['profile'])) {
        $profile = $install_state['parameters']['profile'];
      }

'site' => [],
    ];
    $this->serviceProviderClasses = [
      'app' => [],
      'site' => [],
    ];
    $this->serviceYamls['app']['core'] = 'core/core.services.yml';
    $this->serviceProviderClasses['app']['core'] = 'Drupal\Core\CoreServiceProvider';

    // Retrieve enabled modules and register their namespaces.     if (!isset($this->moduleList)) {
      $extensions = $this->getConfigStorage()->read('core.extension');
      // If core.extension configuration does not exist and we're not in the       // installer itself, then we need to put the kernel into a pre-installer       // mode. The container should not be dumped because Drupal is yet to be       // installed. The installer service provider is registered to ensure that       // cache and other automatically created tables are not created if       // database settings are available. None of this is required when the       // installer is running because the installer has its own kernel and       // manages the addition of its own service providers.       // @see install_begin_request()       if ($extensions === FALSE && !InstallerKernel::installationAttempted()) {
        $this->allowDumping = FALSE;