Zane, as I understand, all related code was removed. Probably we may to remove our Hidden resource too.
If we want to have hidden resource, then probably as you mentioned will be enough to raise Exceptions and execute nothing for handle_delete. On 28 February 2017 at 01:36, Zane Bitter <zbit...@redhat.com> wrote: > On 24/02/17 06:15, Julien Danjou wrote: > >> Hey, >> >> We're about to remove the code for the deprecated combination alarm. >> >> https://review.openstack.org/#/c/429405/ >> >> I checked and as far as I can tell that should not break Heat gate, but >> I'd prefer to be sure. So, Heat developers if you have some code relying >> on it, let us know before we press the big +A button. >> > > Looks like it merged and there was no breakage, so that's good. > > How should we handle the (hidden) resource type in Heat? > > http://git.openstack.org/cgit/openstack/heat/tree/heat/engin > e/resources/openstack/aodh/alarm.py#n227 > > Make handle_delete() return without doing anything, and raise an exception > in all other handle_*() methods? > > - ZB > > > __________________________________________________________________________ > 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 > -- Regards, Sergey.
__________________________________________________________________________ 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
