revi-archive/phorge-phorge
1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-11-22 23:02:42 +01:00
Code Issues Releases Wiki Activity

Don't warn about a locked database value after users run "bin/auth lock"

Browse source 
Summary: Ref T7667. Also one text fix.

Test Plan: Ran `bin/auth lock`, didn't get a replacement setup issue.

Reviewers: amckinley

Reviewed By: amckinley

Maniphest Tasks: T7667

Differential Revision: https://secure.phabricator.com/D20447
This commit is contained in:
epriestley 2019-04-17 17:23:19 -07:00
parent 02cfcfa079
commit c648077625
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
src/applications/config/check/PhabricatorExtraConfigSetupCheck.php
View file

@ -121,6 +121,7 @@ final class PhabricatorExtraConfigSetupCheck extends PhabricatorSetupCheck {
'phabricator.uninstalled-applications',
'phabricator.application-settings',
'config.ignore-issues',
'auth.lock-config',
);
$soft_locks = array_fuse($soft_locks);
if (isset($soft_locks[$key])) {
@ -146,7 +147,7 @@ final class PhabricatorExtraConfigSetupCheck extends PhabricatorSetupCheck {
'that it was previously not locked, you set it using the web UI, '.
'and it later became locked.'.
"\n\n".
'You should copy this configuration value in a local configuration '.
'You should copy this configuration value to a local configuration '.
'source (usually by using %s) and then remove it from the database '.
'with the command below.'.
"\n\n".