Feature redis insight#2793
Open
spicecadet wants to merge 2 commits intopantheon-systems:4.xfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've been working on four new Redis commands for terminus - (connect, flushdb, info with 9 sub-commands, and insight). I also included comprehensive functional tests covering all 12 command methods.
My idea is to make some of the common tasks that I run a little easier to enable developers who are not familiar with Redis to execute. Connect opens redis-cli and Redis Insight opens Redis Insight (similar to how terminus pancakes opens a db app) and creates a connection. Info and it's sub-commands get stats based around the INFO command and Flushdb flushes Redis.
The Insight command currently works on Mac, but I'm not sure what it would take to get it working for Linux and Windows. Additionally, the flushdb command could be risky if run in production and it may be a good idea to prompt the user to make sure they realize they are flushing production environment.