Description
Problem
Often, operators need to invoke clear packets
CLI and run that in parallel with hermes start
. Currently we don't support this use case: the start
process has to be stopped first, before invoking clear packets
; or alternatively a different config.toml has to be used for clear packets
to ensure non-concurrent access to the wallet that start
process is using.
We plan to make it more convenient by supporting a specific wallet for the clear packets
(ref: #2111) command, so that in the future this CLI can run in parallel with start
.
Proposal
Another way to should support the use-case of live packet clearing is by leveraging our REST API: adding a new endpoint clear-packets
that allows to trigger a packet clearing on an already executing start
instance. Ideally, this new endpoint can also be parametrized with a specific chain identifier, eg clear-packets/ibc-0
to trigger packet clearing specifically on all paths that have packets originating from ibc-0
.
Acceptance Criteria
- permit operators to trigger packet clearing on a running
start
instance via the REST API
For Admin Use
- Not duplicate issue
- Appropriate labels applied
- Appropriate milestone (priority) applied
- Appropriate contributors tagged
- Contributor assigned/self-assigned