9cfd6fc760
Make aggregate.create() and destroy() use the API rather than cell database. Also block aggregate creation until main database empty. This makes Aggregate.create() fail until the main database has had all of its aggreagtes migrated. Since we want to avoid any overlap or clashes in integer ids we need to enforce this. Note that this includes a change to a notification sample, which encodes the function and module of a sample exception (which happens to be during an aggregate operation). Since the notifications are encoding internal function names, which can and will change over time, this is an expected change. blueprint cells-aggregate-api-db Co-Authored-By: Dan Smith <dansmith@redhat.com> Change-Id: Ida70e3c05f93d6044ddef4fcbc1af999ac1b1944 |
||
---|---|---|
.. | ||
add-aggregate-type-extra-specs-affinity-filter-79a2d3ee152b8ecd.yaml | ||
aggregate-uuid-generation-1f029af7a9af519b.yaml | ||
aggregates-moved-to-api-database-e1bd30909aaf79d3.yaml |