rleenders / cassandra-migrate Goto Github PK

Migration files are created and execution happens in the current working directory (process.cwd).
A directory could be created for the migrations, cd into it and run the commands in there.

It would be more user-friendly if the migrations directory could be specified in the options, so the migration scripts can be run from the project root (thus more easily via npm run).

Can't have a migration that will create a keyspace because the package trying to create sys_cassandra_migrations before first migration run
For example a command fail
cassandra-migrate up -k test -u cassandra -p cassandra
if test keyspace not exists and I want to run a migration with
CREATE KEYSPACE IF NOT EXISTS test WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 1 };

instead of relying solely on desired state migration specification which can get unclear at times (if I roll back to migration N, does that include rolling back N or keeping N applied, how to roll back all migrations including the 1st one, etc)

it would be smart to include explicit directional commands ie:
cassandra-migrate apply (to increment up one migration)
cassandra-migrate apply -a (to run all pending migrations)
cassandra-migrate apply -n ( to migrate up to and including a specified migration)

cassandra-migrate rollback (to rollback one migration)
cassandra-migrate rollback -a (to rollback all applied migrations)
cassandra-migrate rollback -n (to rollback down to and including the specified migration)

this should also simplify some of the parsing since we know explicitly which direction the user intends to go

Problem: The template file fix ( #15 ) was merged over a year ago but isn't published yet.

add a status command to show the following

1. latest applied migration
2. all applied migrations
3. all migrations available but not applied

Add some functionality to manually enter a migration in the migration table