Refactor activity triggers to include input parameters and comment out waiting logic in orchestrator

Author: AnatoliB

samples-v2/orchestration_versioning/function_app.py

@@ -33,9 +33,9 @@ def my_orchestrator(context: df.DurableOrchestrationContext):
         activity_result = yield context.call_activity('activity_b')
 
     # Provide an opportunity to update and restart the app
-    context.set_custom_status("Waiting for Continue event...")
-    yield context.wait_for_external_event("Continue")
-    context.set_custom_status("Continue event received")
+    # context.set_custom_status("Waiting for Continue event...")
+    # yield context.wait_for_external_event("Continue")
+    # context.set_custom_status("Continue event received")
 
     # New sub-orchestrations will use the current defaultVersion specified in host.json
     sub_result = yield context.call_sub_orchestrator('my_sub_orchestrator')
@@ -45,10 +45,10 @@ def my_orchestrator(context: df.DurableOrchestrationContext):
 def my_sub_orchestrator(context: df.DurableOrchestrationContext):
     return context.version
 
-@myApp.activity_trigger()
-def activity_a() -> str:
+@myApp.activity_trigger(input_name="input")
+def activity_a(input: str) -> str:
     return f"Hello from A!"
 
-@myApp.activity_trigger()
-def activity_b() -> str:
-    return f"Hello from B!"
+@myApp.activity_trigger(input_name="input")
+def activity_b(input: str) -> str:
+    return f"Hello from B!"