openstack/grenade
Code Issues Proposed changes

ensure that grenade db is fresh on each run

Browse Source 
The grenade db is really just an ini file, but there is no reason why
it should persist in a second run of grenade, and it actually causes
issues if it does. Blank it out in the init phase to ensure we're
starting with a blank store.

Change-Id: I22a2b53739153011f5c250739278719259ad7860
This commit is contained in:
Sean Dague 2015-04-16 06:53:55 -04:00
parent a88dd83270
commit 9bf1482680
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
inc/plugin
View File

@ -84,11 +84,10 @@ function resources {
done
}
# initialize the grenade_db and ensure that it's blank for each run
function init_grenade_db {
if [[ ! -e $GRENADE_DB ]]; then
mkdir -p $SAVE_DIR
touch $GRENADE_DB
fi
mkdir -p $SAVE_DIR
echo "" > $GRENADE_DB
}
function resource_save {