2021-02-11 15:25:42 UTC - Matt Rutkowski: @David Williams You can create a manifest(.yaml) file that defines your packages, actions, triggers, rules, etc. then use wskdeploy to deploy all those things (i.e., create them in the correct order and associate them and put them in the defined namespaces with any parameters defined). Then all you need do is let automated triggers (already deployed) run or manully invoike your actions using `wsk invoke` https://openwhisk-team.slack.com/archives/C79ALSWJJ/p1613057142020900 ---- 2021-02-11 15:27:28 UTC - Matt Rutkowski: you an add the `web: true` attribute to any action (within the manifest file) to make it web accessible (i.e., have OW generate a public endpoint for it) and you can manipulate the HTTP headers within the action to control mime types, etc. https://openwhisk-team.slack.com/archives/C79ALSWJJ/p1613057248022600 ---- 2021-02-11 15:30:21 UTC - Matt Rutkowski: The manifest is a means to capture your “model” of your application’s actions within a single manifest file and create them with one command (repeatability); it also provides higher order functions to track/sync manifests (b/w client and server) as well, but that is a more advanced discussion white_check_mark : David Williams https://openwhisk-team.slack.com/archives/C79ALSWJJ/p1613057421025100 ---- 2021-02-11 15:31:48 UTC - Matt Rutkowski: Here is the canonical docs on “web actions” <https://github.com/apache/openwhisk/blob/master/docs/webactions.md> https://openwhisk-team.slack.com/archives/C79ALSWJJ/p1613057508025600 ---- 2021-02-11 15:32:12 UTC - Matt Rutkowski: and a nice article from Rodric: <https://medium.com/openwhisk/whats-new-web-actions-e0ffeef1bea3> https://openwhisk-team.slack.com/archives/C79ALSWJJ/p1613057532026000 ----
