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

Make Cosmovisor use cobra #11789

Closed
4 tasks
julienrbrt opened this issue Apr 26, 2022 · 0 comments · Fixed by #11823
Closed
4 tasks

Make Cosmovisor use cobra #11789

julienrbrt opened this issue Apr 26, 2022 · 0 comments · Fixed by #11823
Assignees
Labels
C:Cosmovisor Issues and PR related to Cosmovisor good first issue

Comments

@julienrbrt
Copy link
Member

Summary

Currently, Cosmovisor does not use cobra.
As the tool is expanding, and we are adding more functionalities, it starts to feel hacky.
Please refactor Cosmovisor to use cobra.

Pitfall: #10316 (comment)


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@julienrbrt julienrbrt added C:Cosmovisor Issues and PR related to Cosmovisor good first issue labels Apr 26, 2022
@julienrbrt julienrbrt self-assigned this Apr 28, 2022
@julienrbrt julienrbrt moved this from Ready to In Progress in Cosmos SDK Maintenance Apr 28, 2022
@julienrbrt julienrbrt linked a pull request Apr 28, 2022 that will close this issue
19 tasks
@julienrbrt julienrbrt moved this from In Progress to In Review in Cosmos SDK Maintenance Apr 29, 2022
@mergify mergify bot closed this as completed in #11823 May 2, 2022
mergify bot pushed a commit that referenced this issue May 2, 2022
## Description

Closes: #11789



---

### Author Checklist

*All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.*

I have...

- [x] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] added `!` to the type prefix if API or client breaking change
- [x] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting))
- [x] provided a link to the relevant issue or specification
- [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/building-modules)
- [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing)
- [x] added a changelog entry to `CHANGELOG.md`
- [x] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [ ] updated the relevant documentation or specification
- [x] reviewed "Files changed" and left comments if necessary
- [ ] confirmed all CI checks have passed

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)
Repository owner moved this from In Review to Done in Cosmos SDK Maintenance May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:Cosmovisor Issues and PR related to Cosmovisor good first issue
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant