Drush 12 don't see some settings that are added via require_once in settings.php

This is not the configuration system. This is not a bug in Drupal. You are running a custom setup using PHP language primitives like require_once.

Probably $settings['hash_salt'] is being unset or set to an empty string in sites/settings.php.

We see a similar behavior after having upgraded to Drush 12.

We also include a different file in our settings.php. We needed to replace our include_once with include to make it work.

@BadWebCoder, has this been resolved? If so, adding a comment of what was done can help others. Thanks

The status has been set to `Maintainer needs more info`. What kind of info is requested here?

The problem still persist for us. Any require_once and include_once are misbehaving for us. It's not a big deal, we can easily change it to the without `_once` function. Not sure if it is drush or Drupal core causing it.

bumping 1 more time, I don't have an answer to #5 but don't want to close just yet.

I don't think Drupal can have any influence directly over the behavior of require, require_once, include, or include_once in PHP. Perhpaps the file has already been included in a prior bootstrap phase which overwrote values. @szeidler or @szeidler: have you traced Drush's execution to the point of the require to investigate?

I meant @badwebcoder or @szeidler...

In case my comment was vague, I am saying that the most likely situation is that the file has already been included by some other code, and that proving that should be straightforward on your end using built-in PHP debugging tools.