Eager load an event's resource properties data in the list_events
"show event" case, i.e. when an event uuid is specified. When showing
multiple events, the events' resource properties data should not be
eager loaded.
Change-Id: I12e371dcbdae398360e28200e68f4a75831f8f17
Closes-bug: #1665506
Typically when retrieving a large number of events, we don't need to
load resource_properties_data for each event.
Change-Id: I6564fea91d19c24409075152a614cc036dc1ee34
Add the resource_properties_data association to resource and event
objects. The resource and event engine objects do not use yet
it but will soon.
Change-Id: Idecaafffbc5e9bfcd2355e2a165836a5ed89b16f
The db.api module provides a useless indirection to the only
implementation we ever had, sqlalchemy. Let's use that directly instead
of the wrapper.
Change-Id: I80353cfed801b95571523515fd3228eae45c96ae
This change removes the event.Event.load method, and switches
api.format_event to using the Event versioned object instead.
Since the only purpose of loading the stack is to get its identifier,
this is now also coming from a Stack versioned object.
Related-Bug: #1588561
Change-Id: I7b1fc99894818b44cde08cf08b010b1d1fb94e9f
In Heat objects, the default value of nullable attribute is
set in many of the object's fields, which is not required
as oslo object Field defines nullable as False by default
Change-Id: I0164b64c043816f624aeba19561a4a5f8d36689d
Closes-bug: #1439957
liyi