Crag Wolfe 57c5aae88b De-duplicate properties_data between events, resources ... Properties data (encrypted or not) is now stored in the resource_properties_data table. We still support reading properties data from the legacy locations (separate columns in the resource and event tables) but all new properties data are written to resource_properties_data. Instead of duplicating properties data for a given resource and its events, we refer to the same resource_properties_data object from both resources and events. Notes about encrypting/decrypting properties data: 1. ResourcePropertiesData takes care of encrypting/decrypting, so consumers (events and resources) don't have to worry about it. 2. Previously (not anymore), heat.engine.resource would take care of the encrypting in _store() and _store_or_update(). 3. Previously and currently, heat.object.resource decrypts the legacy properties_data field if needed. Change-Id: I569e16d4a7d3f5ccc22d57fe881c4fd5994677ac Closes-Bug: #1524013		2017-01-24 15:40:10 -08:00
..
sqlalchemy	De-duplicate properties_data between events, resources	2017-01-24 15:40:10 -08:00
__init__.py	Do not initialize anything during import phase	2013-04-24 10:03:06 -07:00