You Don't Need To Set The $Drupal_Hash_Salt At All:
It is true that the hash salt is required to run drupal; The process method of this class regenerates the hash_salt every time. If your settings.local.php needs adding just use this and it will work for you after a cache reload $settings['hash_salt'] = 'change_this';
Instantly Share Code, Notes, And Snippets.
The installer sets it, and you shouldn't change it (unless you have some special reason to do so). It stands for secure hash algorithm 1. This allows for a couple of small clean ups too.
So , One Of The Features Is The Login/Authenticate Function.
Just removing the already deprecated function. Drush eval var_dump (drupal\component\utility\crypt::randombytesbase64 (55)) Please mind that string is case sensitive!
Code Using This Will Die.
Function process() { if (drush_drupal_major_version() >= 8) {. This function instantiates the class provision_config_drupal_settings and writes the settings.php. My reasoning is that drupal uses the salt when checking the validity of passwords and if you're saving unsalted sha512 passwords they won't decode correctly when drupal uses the salt.
Drush @Pantheon.sitename.dev Ev 'Return Getenv (Drupal_Hash_Salt)'.
Generate a long random salt using a csprng. Add a line to your local settings.php like: Select the checkbox to include salt and specify the salt or use the default value;