datastax-labs/astra-cli

DataStax Astra automation CLI https://astra.datastax.com

astra-cli's Issues

Polish up command calls

We should never have ./bin/whatever. It is fragile (doesn't work everywhere) and looks immature.

We should get and put the bundle in a specific place (maybe ~/.config/astra/bundle?) or use the .astrarc/.env file

It should be called "astra" not "astra-cli" to match with other cli's out there.

empty command should list help

error in help text for user and keyspace

-k, --keyspace string keyspace user to give to the Astra Database
-n, --name string name to give to the Astra Database

these two are actually reversed in meaning

test login against new IAM api

• this was broken in beta, test again with IAM

up test coverage

test coverage needs to be at least 80%

rename executable to astra

running login with no args should bring up promps asking for token

display version support when running

• need to update build to automatically change version to match the tag
• all commands should display astra version
• provide version subcommand to generate easily parsable version

fix goreport card fully

https://goreportcard.com/report/github.com/rsds143/astra-cli

mostly code comments

add screenshots and docs for creating an token with rights for devops api

• need a list of rights that one has to have to use the tooling
• should have some indication of where to do this in the astra UI screenshot or description

improve progress

the current progress leaves a lot to be desired and we just get
2021/09/28 15:32:04 waiting
2021/09/28 15:32:35 waiting

replace this with just simple dots I guess?

Inline Login Messaging

Add inline login messaging for token generation

"json" in output

Is there really an extra "json" in the output here? It should just be the json file, for piping to jq or whatever.

./bin/astra-cli db get 2c3bc0d6-5e3e-4d77-81c8-d95a35bdc58b -o json
json
{

implement v2.0 api

https://docs.datastax.com/en/astra/docs/_attachments/devopsv1.html

remove ./bin from docs

update docker image to point to datastax based repository

atm this is pointing to my personal docker account, and as I am leaving the company this is not longer term something that makes sense.

Another alternative is just to remove docker

Cover all Devops endpoints

Ensure we are covering all https://docs.datastax.com/en/astra/docs/_attachments/devopsv2.html endpoints.

add schema operations

need to add schema operations to the tooling and potentially some basic data commands (maybe executing CQL? hard to say)

support basic mutations

We should cover the whole range of common tasks - create a db, add a row, create a table, update a row, delete a row, delete a row, delete a table, delete a database.

We should allow for ingestion of a json file with operations to execute.

add to homebrew

create curl bash install script

With home-brew does the executable really go into ./bin?

Most people will have no idea which release they need. Please make a Mac/Linux/Win executable. On first run it should:

• Install the binary into the path or add the binary path to the PATH
• Run astra-setup, which guides you to get a token (which currently just populates .astrarc and .env but could pull the bundle)

download secure connection bundle

do not presently have a command to download the secure connection bundle

docker image and script to run it

this will help make automation even easier for some and certainly make it easier to run workflows in kubernetes

automate release on tags

snapcraft

readme has typo in workflow

(https://github.com/datastax/astra-cli/actions/workflows/go.yaml/badge.svg)]
should be

(https://github.com/datastax-labs/astra-cli/actions/workflows/go.yaml/badge.svg)](

WaitUntil doesn't wait long enough in Astra cluster creation

When creating a E-tier cluster in Astra, we often encounter the following error:

$ astra -e dev db create -l AWS -k testks -n clitest -r us-east-1 -t E60
..........................................................................................unable to create '{1 AWS testks clitest <nil> us-east-1 E60 <nil>}' with error waiting for status check on create db failed because 'unable to find db id aae7d687-1083-4c04-915c-fdf79a2cef84 with status [ACTIVE] after 2700 seconds'

This can be easily fixed by allowing it to wait for 1 hour instead of 2700 seconds.