Update patch set 11

Patch Set 11: Code-Review+1

(1 comment)

Patch-set: 11
Reviewer: Gerrit User 8042 <8042@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
Label: Code-Review=+1
Attention: {"person_ident":"Gerrit User 7144 \u003c7144@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"Jiří Stránský replied on the change"}

3b2b55a9e238cd3f88e6c41d913896202b51f9e2

@@ -0,0 +1,27 @@
+{
+  "comments": [
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "4c7df798_487b58c3",
+        "filename": "specs/yoga/taskcore-directord.rst",
+        "patchSetId": 11
+      },
+      "lineNbr": 238,
+      "author": {
+        "id": 8042
+      },
+      "writtenOn": "2021-10-29T13:49:32Z",
+      "side": 1,
+      "message": "For operations similar to what is currently handled by these playbooks? https://github.com/openstack/tripleo-ansible/tree/master/tripleo_ansible/playbooks\n\nIt would be even more powerful if such workflows could be emitted from the composable services framework, so that multiple services could contribute their pieces into arbitrarily named workflows, just like they contribute into deployment/update/upgrade. The deploy/update/upgrade workflows would then become just \"well knowns\" within a generic workflow building mechanism. I do not have a particular use case in mind for this though, just throwing it out as a \"what if\" idea.",
+      "range": {
+        "startLine": 236,
+        "startChar": 0,
+        "endLine": 238,
+        "endChar": 10
+      },
+      "revId": "3b2b55a9e238cd3f88e6c41d913896202b51f9e2",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    }
+  ]
+}