*`leap db destroy --db sessions,tokens` You can ignore message about needing
*`leap db destroy --db sessions,tokens` You can ignore message about needing to redeploy (since, in this case, we just want to permanently delete those databases).
to redeploy (since, in this case, we just want to permanently delete those
*`leap test` to make sure everything is working
databases).
New features:
New features:
* rotating couchdb databases
* rotating couchdb databases: CouchDB is not designed to handle ephemeral data, like sessions, because documents are never really deleted (a tombstone document is always kept to record the deletion). To overcome this limitation, we now rotate the `sessions` and `tokens` databases monthly. The new database names are `tokens_XXX` and `sessions_XXX` where XXX is a counter since the epoch that increments every month (not a calendar month, but a month's worth of seconds). Additionally, nagios checks and `leap test run` now will create and destroy test users in the `tmp_users` database, which will get periodically deleted and recreated.
* deployment logging: information on every deploy is logged to
* deployment logging: information on every deploy is logged to `/var/log/leap` on the node, including the user, leap_cli version, and platform version.
`/var/log/leap`, including the user, leap_cli version, and platform version.
* you must now run `leap deploy --downgrade` if you want to deploy an older version over a newer platform version.
* you must now run `leap deploy --downgrade` if you want to deploy an older
* the install source for each custom daemons (e.g. tapicero, etc) can now configured in `common.json`.
version over a newer platform version.
* a summary of deploys is logged on each node at `/var/log/leap/deploy-summary.log`
* the install source each custom daemons (e.g. tapicero, etc) is now