App will maintain a table of up or down state of the database keyspace.

Builds for different platform deliverables.

dotnet publish -c Release -r linux-x64 --self-contained true

dotnet publish -c Release -r linux-musl-x64 --self-contained true

dotnet publish -c Release -r win-x64 --self-contained true

dotnet publish -c Release -r rhel-x64 --self-contained true

dotnet publish -c Release -r osx.10.14-x64 --self-contained true

dotnet publish -c Release -r osx.10.13-x64 --self-contained true

For each of these the respective mapping to OS in order is as follows:

1. Linux x64 Debian distro/Ubuntu distros.
2. Linux musl for Alpine Distro.
3. Windows x64 Portable (Win7+?)
4. Red Hat Linux x64
5. OS-X / MacOS 10.13 High Sierra
6. OS-X / MacOS 10.14 Mojave

App will provide a way to create the initial keyspace based on various requirements on configuration such as strategy, replication factor, etc.

Docs are setup currently to use the repo (i.e. Github Pages with the README.md) which should be fine, unless someone wants to elaborate and extend this. Ideally using the same model but adding documentation and some information organization and navigation.

Setup the CLI so that it can be used with things like Vault, or other tooling or even environment variables for execution of CQL.

Finish Wire Up of CLI to Functional Library.

Design a logo, something around the Cassandra theme would be cool.

Currently the binaries for each OS bloat up to about ~70mb. If you've got some build chops, it'd be great to make them smaller! :)

Fix Tests so Cluster is Derived from configuration based IP.

The IP for tests, or whatever the CLI is running against should be derived from a configuration setting and not statically used via magic string variable in the tests.

App will take cql files based on date, time, and up or down keyword for migrations up of data schema.

Will want a getList of files too.

i.e. https://github.com/anthonyreilly/ConsoleArgs/blob/master/Program.cs

Wire up options, sub commands, etc.

App will execute the cql files in order dated by date time.

As per discussion on stream, we discussed moving the ReadAllText from the FileSelection to the point that we need to actual execute the script

User wants to be able to migrate up to X version or down to Y version.

i.e.

migrate up -v 1.4

migrate down -v 3.2

migrate up -v 3.2

migrate down -v 1.4

Something similar to those commands.

A record needs written for each up or down migration to whatever versioned point one migrates to.

App will store connection information pertinent to the database that it is or needs to be working against.