If you attempt to update a stack containing
OS::Heat::SoftwareDeployments resources, so it uses the new
non-deprecated OS::Heat::SoftwareDeploymentGroup type instead, it
deletes the group, and all of the deployments.
This means that any deployment "actions" property will be
misinterpreted, e.g if you have actions: CREATE, all the deployments
will re-run on the update, even though it's an update, not a create.
This issue exists on all deprecated resoruces, when we trying to upgrade
to new version of it by update.
This patch fix above update issue by check if resoruce was deprecated
and been update by replacing resource (which is the parent class of
existing resource).
Change-Id: Ib7880120a90c4497a7ceea53eee55c220a28d14e
Closes-Bug: #1528958
Validates the resource_type's support_status when it is
searched from global ResourceRegistry. This saves user from
searching for invalid support status.
implements blueprint heat-resource-type-search
Change-Id: I620ead91b024b369e4f2d8971f1190da61cfc0b2
Add HIDDEN status to SupportStatus and it's supporting
in code: hiding objects with HIDDEN status in docs and
resousce-type-list.
bp deprecating-improvements
Change-Id: Iebd77d769966bab321aeaf3e23b7f54e9456ad13
Add previous_status parameter to SupportStatus for
better understanding of objects life cycles.
bp deprecating-improvements
Change-Id: I447d001ada9b0a0297de79704d91e263934a185f
This improve doc notes about deprecated objects
and adds option 'version' to all objects with
support_status parameter.
blueprint deprecating-improvements
Change-Id: I82f9f4514142a3a66c872722b265fee365eb5de2
Since i18n.install() is deprecated, remove it from heat codes and
import i18n._() to where it needed.
blueprint oslo-i18n
Change-Id: Icefada18b5a33112b425cd90d31d3a6a5f06188a
Andreas Jaeger