I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones.<p>For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe.<p>Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launching being the track to promotion explain some of the state of things within GCP.
This is an interesting accommodation to less terminal savvy users. I'm not interested personally. But, it's an interesting concept.<p>In fact, I think it would be an interesting thing to standardize, like super-completion.<p>Someone else in this thread mentioned that Amazon is working on a similar interactive shell [0], and there is a whole group of tools like this for database CLI's [1], including PostgreSQL, MySQL, MS-SQL, and VerticaDB.<p>It's a shame that each of these projects have to somewhat re-invent the wheel (though prompt-toolkit does a lot of heavy lifting [2]). And it's even more of a shame that each of these tools require a seperate environment. So, you have to exit Google's interactive shell to do something in AWS.<p>[0] <a href="https://github.com/awslabs/aws-shell" rel="nofollow">https://github.com/awslabs/aws-shell</a><p>[1] <a href="https://www.dbcli.co" rel="nofollow">https://www.dbcli.co</a><p>[2] <a href="https://github.com/jonathanslenders/python-prompt-toolkit" rel="nofollow">https://github.com/jonathanslenders/python-prompt-toolkit</a>
AWS also has something similar called AWS Shell: <a href="https://github.com/awslabs/aws-shell" rel="nofollow">https://github.com/awslabs/aws-shell</a>
Is this an open-source library one could use to make one's own interactive tools? Just curious. Anyone have pointers?<p>Edit: I am slightly familiar with this family of tools. I was curious if there was a pointer to exactly the one used here.
This is awesome, interactive CLIs are great for simple use cases. I hope they continue to have support for non-interactive scenarios so that automation can continue to work (apologies if I missed that in the article).
While we're on the topic, Cool Retro Term is open source or free and so much fun to play with. I have a real thing for the amber monitors. I got to see some ancient ones still operating the world in my early career on the dying open outcry trading floors of the American Stock Exchange in the mid 2000s.
LMGTFY:
<a href="https://www.google.com/search?q=amber+monitor&tbm=isch&source=iu&ictx=1&fir=fSfNUPwGxeGIkM%253A%252CLlwr8x3vofq4uM%252C_&usg=__RCbknmO0-AkNOKAPEQDQJhy_kig%3D&sa=X&ved=0ahUKEwj-wa_GlvHZAhVPS60KHagxDSkQ9QEIKzAB#imgdii=rXdOkNyK8fLPnM:&imgrc=k03wa8hB-41R6M" rel="nofollow">https://www.google.com/search?q=amber+monitor&tbm=isch&sourc...</a>:
missing good old googlecl which Google killed themselves by making OAuth2 mandatory and not beeing able to switch from OAuth1 to OAuth2 in their own command line tool: <a href="https://code.google.com/archive/p/googlecl/issues/573" rel="nofollow">https://code.google.com/archive/p/googlecl/issues/573</a>
I tried this with kubectl, but it crashed... so I used gcloud feedback to send a stacktrace, it sent me to a page with a 400 response.<p>Overall, seems a bit too early to start promoting this for any real use.
I made something even better. Its for AWS though: <a href="https://github.com/svolpe43/cfsh" rel="nofollow">https://github.com/svolpe43/cfsh</a>
LOL @ the bright green on black terminal pictures. How shall I say it, it feels very "l33t". Too bad they didn't use more normal terminal colours, it would improve readability IMO.