Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hermes support for triggering live packet clearing #2207

Open
3 of 6 tasks
adizere opened this issue May 11, 2022 · 0 comments
Open
3 of 6 tasks

Hermes support for triggering live packet clearing #2207

adizere opened this issue May 11, 2022 · 0 comments
Labels
A: good-first-issue Admin: good for newcomers O: new-feature Objective: cause to add a new feature or support O: usability Objective: cause to improve the user experience (UX) and ease using the product
Milestone

Comments

@adizere
Copy link
Member

adizere commented May 11, 2022

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
@adizere adizere added O: new-feature Objective: cause to add a new feature or support A: good-first-issue Admin: good for newcomers O: usability Objective: cause to improve the user experience (UX) and ease using the product labels May 11, 2022
@adizere adizere added this to the v1.2 milestone May 11, 2022
@adizere adizere modified the milestones: v1.2, v2 Jun 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: good-first-issue Admin: good for newcomers O: new-feature Objective: cause to add a new feature or support O: usability Objective: cause to improve the user experience (UX) and ease using the product
Projects
None yet
Development

No branches or pull requests

1 participant