Crag Wolfe 98505288b2 Add heat-manage subcommand to migrate legacy prop. data ... Add a subcommand to heat-manage to migrate resource and events properties data from the legacy db locations to the new. I.e., migrate properties data out of the legacy columns in the resource and event tables into the recently added resource_properties_data table. No attempt at de-duplication between resources and events is made for the migration: a new row is created in resource_properties_data for every row that has legacy properties data in the resource or event tables. Change-Id: I364d509c357539d1929eb2e40704e60049469ea2		2017-01-31 13:45:52 -08:00
..
__init__.py	Add a basic heat-manage	2013-05-27 21:06:31 +10:00
all.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
api.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
api_cfn.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
api_cloudwatch.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
engine.py	heat-all: all-in-one heat launcher	2016-10-13 11:49:15 -04:00
manage.py	Add heat-manage subcommand to migrate legacy prop. data	2017-01-31 13:45:52 -08:00