Not really. Ideally, you need to write your resource such that these changes are backwards compatible. We do this for the resources we ship with Heat (add new properties while supporting deprecated properties for several releases).
On Apr 11, 2016, at 1:06 PM, "Praveen Yalagandula" <yprav...@avinetworks.com> wrote: > Hi, > > We are developing a custom heat resource plug-in and wondering about how to > handle plug-in upgrades. As our product's object model changes with new > releases, we will need to release updated resource plug-in code too. However, > the "properties" stored in the heat DB for the existing resources, whose > definitions have been upgraded, need to be updated too. Was there any > discussion on this? > > Thanks, > Praveen Yalagandula > Avi Networks > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
