docs: Add blazar project to Cosmos SDK external tooling readme section #23012
Conversation
📝 WalkthroughWalkthroughThe pull request updates the documentation in Changes
Possibly related PRs
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs/build/tooling/README.md (1)
25-25: Consider adding a brief description for BlazarTo maintain consistency with other tools and help users understand Blazar's purpose, consider adding a brief description.
-* [Blazar](https://github.com/ChorusOne/blazar) +* [Blazar](https://github.com/ChorusOne/blazar) - A comprehensive network upgrade management service featuring UI, notifications, and automated checks
📜 Review details
Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/build/tooling/README.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/build/tooling/README.md (1)
Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"
🔇 Additional comments (1)
docs/build/tooling/README.md (1)
23-23: LGTM! Description accurately reflects tool diversity
The updated description better encompasses both operational and development tools in the ecosystem.
julienrbrt
changed the title
Description
Blazar is a standalone service designed to interact with the Cosmos SDK node, specifically handling all types of network upgrades.
It serves as an alternative to Cosmovisor with an extensive feature set, including a user interface (UI), Slack notifications, an optional SQL database for ad-hoc upgrade scheduling, and comprehensive pre- and post-upgrade checks.
You can learn more about Blazar here.
Why this Pull Request?
Blazar provides significant value to the Cosmos ecosystem by simplifying the network upgrade process for validator operators. While Cosmovisor has been a useful tool, it did not fully meet our needs at Chorus One. Consequently, we developed Blazar to address these gaps.
We believe other network operators will find Blazar to be a substantial improvement, enhancing their day-to-day operations.
Is Blazar actively maintained?
Yes, Blazar is actively maintained and used for the majority of Cosmos SDK network upgrades at Chorus One. It has been rigorously tested, both through integration and unit tests, and is regularly applied in real-world scenarios, approximately on a weekly basis.
Summary by CodeRabbit