fix --describe-other-params of external when encryption is not specified
Encryption not being specified makes lenientRemoteConfigParser fail to parse, and so it was not able to start the external up to get LISTCONFIGS.
This commit is contained in:
parent
2be4122bfc
commit
830c30001b
1 changed files with 17 additions and 14 deletions
|
@ -784,8 +784,11 @@ getInfoM external = (++)
|
|||
{- All unknown configs are passed through in case the external program
|
||||
- uses them. -}
|
||||
lenientRemoteConfigParser :: RemoteConfigParser
|
||||
lenientRemoteConfigParser = addRemoteConfigParser specialRemoteConfigParsers $
|
||||
RemoteConfigParser
|
||||
lenientRemoteConfigParser =
|
||||
addRemoteConfigParser specialRemoteConfigParsers baseRemoteConfigParser
|
||||
|
||||
baseRemoteConfigParser :: RemoteConfigParser
|
||||
baseRemoteConfigParser = RemoteConfigParser
|
||||
{ remoteConfigFieldParsers =
|
||||
[ optionalStringParser externaltypeField
|
||||
(FieldDesc "type of external special remote to use")
|
||||
|
@ -826,7 +829,7 @@ remoteConfigParser c
|
|||
-- cases the lenient parser will do the same thing as the strict
|
||||
-- parser.
|
||||
| M.null (M.filter isproposed c) = return lenientRemoteConfigParser
|
||||
| otherwise = case parseRemoteConfig c lenientRemoteConfigParser of
|
||||
| otherwise = case parseRemoteConfig c baseRemoteConfigParser of
|
||||
Left _ -> return lenientRemoteConfigParser
|
||||
Right pc -> case (getRemoteConfigValue externaltypeField pc, getRemoteConfigValue readonlyField pc) of
|
||||
(Nothing, _) -> return lenientRemoteConfigParser
|
||||
|
|
Loading…
Reference in a new issue