Convert WaitConditionHandle to use handle_signal

The metadata_update interface does pretty much the exact same thing
as handle_signal, with the disadvantage that it's not exposed via
the native ReST API, so convert WaitConditionHandle to use
handle_signal.

This has the following advantages:
- Provides a step towards native waitcondition resources
- Enables signalling existing waitcondition resources via
  heat resource-signal (e.g the native API)
- Moves towards a standardized model where handle_signal is the
  only supported plugin interface for asynchronous signalling of
  resources.

To avoid breaking any CD folks who may not update heat-engine and
heat-api-cfn at the same time, the existing resource interface is
maintained with a deprecation warning (how long to maintain this
is TBC).

Change-Id: I453a24f78095dfa5b3a5311651b5f1ac40aa8b3f
blueprint: native-waitcondition

1 files changed, 2 insertions, 3 deletions

diff --git a/heat/tests/test_metadata_refresh.py b/heat/tests/test_metadata_refresh.py
index d7bcde5c3..edf1c62b5 100644
--- a/heat/tests/test_metadata_refresh.py
+++ b/heat/tests/test_metadata_refresh.py
@@ -243,11 +243,10 @@ class WaitCondMetadataUpdateTest(HeatTestCase):
         '''
         1 create stack
         2 assert empty instance metadata
-        3 service.metadata_update()
+        3 service.resource_signal()
         4 assert valid waitcond metadata
         5 assert valid instance metadata
         '''
-
         self.stack = self.create_stack()
 
         watch = self.stack['WC']
@@ -258,7 +257,7 @@ class WaitCondMetadataUpdateTest(HeatTestCase):
             self.assertIsNone(inst.metadata_get()['test'])
 
         def update_metadata(id, data, reason):
-            self.man.metadata_update(utils.dummy_context(),
+            self.man.resource_signal(utils.dummy_context(),
                                      dict(self.stack.identifier()),
                                      'WH',
                                      {'Data': data, 'Reason': reason,