[feature]: support multiple outgoing channel IDs in lncli

[The34Goon]

I want to pay an invoice using either all channels except A B C or define them X Y Z

lncli payinvoice --timeout 20m --fee_limit 35 --outgoing_chan_id XXX YYY ZZZ --pay_req
results in only XXX being used.

lncli payinvoice --timeout 20m --fee_limit 35 —outgoing_chan_id XXX —outgoing_chan_id YYY —outgoing_chan_id ZZZ --pay_req
results in only ZZZ being used.

response when using the --outgoing_chan_ids flag described in api-docs
[lncli] flag provided but not defined: -outgoing_chan_ids

LND_0.16.4-beta

what am I missing?

[alexbosworth]

The API docs don't describe LNCLI, they describe the API that LNCLI uses

[guggero]

As suspected, the command line only takes a single parameter and adds it to the outgoing_chan_ids of the RPC call: https://github.com/lightningnetwork/lnd/blob/master/cmd/lncli/cmd_payments.go#L425

Probably the reason for it is that the CLI library doesn't offer a Int64SliceFlag, so we'd need to use a string slice flag and parse it manually.

For your use case it might be simpler to just create a small NodeJS or Python wrapper script that feeds the params into an RPC call.

[markettes]

May I take this one?

[markettes]

By the way, for the query routes call, I would say we need to change it to accept the same as the payment, an array of strings for the outgoing_chan_id. Let me know if I can fix it with this issue. 😄

[markettes]

Solved here:
#8261

[saubyk]

reopening as the pr is not merged yet