Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-7273

Spike: Evaluate if and how we can invoke Serverless functions from the console

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • UI
    • None
    • ODC Sprint 233, ODC Sprint 234

      Description

      We need to understand what the func invoke command line do under the hood and if we can implement the same feature without a backend in the our frontend code.

      Informations by lball1@redhat.com from the Serverless team:

      1. Function Invocation in Dev Console doc: https://docs.google.com/document/d/1kf0LyvncRHQMpVqQJgY-hWL4LJaBjfhDJWrP8rK-CaM/edit
      2. cli demo from 2023-03-15: https://drive.google.com/file/d/1LN4rICmKQvCcmG_nRrq2pdVYbvqiqDCK/view?usp=sharing

      Acceptance Criteria

      1. Answer: is kn func and func the same cli?
      2. Test func invoke and document or comment (in this ticket here) how the cli invokes a serverless function (in detail)
        1. does it create a k8s resource? Is it implemented with a custom resource? Please include some examples (as full JSON/YAML) to invoke the function with the default parameters and changed type, source, data, content type and format.
        2. Can we invoke a function also with kubectl/oc and from our console YAML editor?
        3. How does the CLI receive the response? Please also show a full response structure (JSON/YAML)
        4. Or do we need to run a custom HTTP command to trigger the function? In this case please provide a curl example to trigger it.
      3. Can we create this resource easily from our frontend?

      Additional Details:

      call func invoke with -v=10 to show and extract the network calls.

            avik6028 Avik Kundu
            cjerolim Christoph Jerolimov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: