adds deployed prompt endpoint functionality

[modcarroll]

• Adds the ...deployments/{deployment-id}/generation/text endpoing to the openAPI file in order to use deployed prompts
• Adds an example for calling this endpoint to the action

[modcarroll]

@jwm4 fyi

[theisen1337]

The deployment OpenAPI json works great. But the actions did not work out of the box. Both actions Invoke watsonx deployed prompt API, and Invoke watsonx generation API did not have the extension hooked in.

I had to manually add the action hook for the integration and model_input, deployment_id, watson_api_version.

Invoke watsonx Generation API is also referencing the incorrect variables.

Invoke watsonx deployed prompt API is referencing ran_successful but that variable is not set, or not set correctly. removing that condition fixed the issue.

"variable": "step_606",
            "condition": {
              "and": [
                {
                  "eq": [
                    {
                      "variable": "step_817_result_2",
                      "variable_path": "success"
                    },
                    {
                      "scalar": true
                    }
                  ]
                },
                {
                  "expression": "${step_817_result_2.body.results}.size() > 0"
                }
              ]
            },

Removing the condition for step_817_result_2 in the actions json. fixed the issue.
updated json:

"variable": "step_606",
            "condition": {
              "expression": "${step_817_result_2.body.results}.size() > 0"
            },

Maybe The actions json should be updated to reflected this change, and the README should include hooking up the extension inside of the action in the UI, As it stands when trying to export the extension action json does not include that connection.

[theisen1337]

The actions json does not work as intended on load in to Watson X assistant. For deployed models in WatsonX AI.

Variable is not correctly set and thus the condition that relies on the variable always fails.

[theisen1337]

This does not work in Invoke Watson Deployment prompt API and shows up as missing variable in Invoke watsonx Generation API

[jwm4]

I haven't tried it out yet, but that typically happens when the actions.json file was exported from an older version of the openapi spec. So @modcarroll , I would recommend that you set this up again with the latest openapi spec and then re-do the export of the actions.json file.

[modcarroll]

I believe I fixed this issue - can you check the latest commit and check again?