heat/heat/db/sqlalchemy
ramishra 7af71497ed Don't update status for replaced resource
With I04e7ad90944c2d03ce0e59ba16af9d60d6e01222 we allowed
update of previously-existing resource if replacement
creation has failed during last update. However, we force
update the status of the existing resource to 'COMPLETE'.
Therefore, in the next update if properties/type has not
changed for the resource it won't try to update/replace
the previously existing resource resulting in false positive
of stack updated successfully.

Task: 42194
Change-Id: Icc90a921ec67e49aec2c4acfad72235c57c78421
(cherry picked from commit bfbaab107d)
2021-04-02 05:36:58 +00:00
..
migrate_repo Keep db model and migration scripts in sync 2020-04-07 20:33:50 +05:30
__init__.py Stub out the database access API 2012-03-29 18:02:16 +02:00
api.py Don't update status for replaced resource 2021-04-02 05:36:58 +00:00
filters.py Remove six and python 2.7 full support 2020-04-22 12:23:44 +02:00
migration.py Squash database patches 2019-10-07 10:38:26 +00:00
models.py Remove db api and tables for CloudWatch 2018-01-28 09:35:07 +05:30
types.py Remove usage of sqlalchemy mutables 2015-06-26 11:02:03 +02:00
utils.py Fix iter bug with SQlAlchemy 1.3.23 2021-02-18 09:59:50 +05:30