<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>We touched this on review <a href="https://review.openstack.org/#/c/73205/">https://review.openstack.org/#/c/73205/</a>, and fixed a bit, bringing it up here to further discuss at slightly higher level. </div><div><br></div><div>Let's go over a tiny bit of YAML definition, clarifying terminology on the way.</div><div><br></div><div><div>Current DSL snippet: </div><div>actions:</div><div> my-action</div><div> parameters:</div><div> foo: bar</div><div> response: # just agreed to change to 'results' </div><div> select: '$.server_id' </div><div> store_as: v1</div></div><div><br></div><div>In the code, we refer to action.result_helper</div><div><br></div><div>1) Note that <b>response</b> is not exactly a parameter. It doesn't doesn't refer to data. It's (query, variable) pairs, that are used to parse the results and post data to global context [1]. The terms response, or result, do not reflect what is actually happening here. Suggestions? Save? Publish? Result Handler? </div><div><br></div><div>2) Whichever name we use for this output transformer, shall it be under parameters? </div><div><br></div><div><div>3) how do we call action/task parameters? Think 'model' (which reflects in yaml, code, docs, talk, etc.)</div><div> input and output? (+1)</div><div> in and out? (-1) </div><div> request and response? (-1) good for WebServices but not generic enough</div><div> parameters and results? (ok)</div></div><div><br></div><div>4) Syntax simplification: can we drop 'parameters' keyword? Anything under action is action parameters, unless it's a reserved keyword, which the implementation can parse out. </div><div><br></div><div><div>actions:</div><div> my-action</div><div> foo: bar</div><div><div> task-parameters: # not a keyword, specific to REST_API</div><div> flavor_id:</div><div> image_id:</div></div><div> publish: # keyword</div><div> select: '$.server_id' </div><div> store_as: v1</div></div><div><br></div><div>[1] Save discussing the way we work with data flow, and talking alternatives, to the next time. </div><div><br></div><div>DZ. </div><div><br></div></body></html>