Flexible and extended configuration file

[holgerw]

I would like to suggest a more flexible yaml configuration.

1. Allow every property at the root level, as well as the profile level. Do not require any property at the root level, as long as it is provided at the profile level.

2. Allow the specification of user, password and host in the yaml file

Following is a sample yaml file, and its execution

profiles:
  dev:
    keyspace: schema_dev
    host: localhost
    user: dev_user
    password: dev_pwd
  dev:
    keyspace: schema_prod
    host: db.my.dmain
    user: prod_user
migrations_path: .
replication:
  class: SimpleStrategy
  replication_factor: 3

cassandra-migrate migrate
cassandra-migrate --profile prod --password prod_pwd migrate

Thanks for cassandra-migrate.

[danielkza]

I'm very positive towards 1, but not so sure about 2. Including the credentials means it's somewhat easy to accidentally run a migration in a production database from a developer machine.

Would accepting a separate credentials file (which should be ignored in source control) work for you?

[holgerw]

Yes, your suggestion of the credential file sounds good. Similar to the solution found in Rails, right?

If you would like help in one of the issues, I could try to submit a pull request, but it would be a type of copy, paste and adapt code. Unfortunately I have zero experience with Python.

[fernandezjose]

Another solution to this approach is to use ENV variables in the yaml and then parse it at execution time.

password: {{ENV:PASSWORD}}