Dedicated REST API Endpoint per action with formal openapi definition

SUMMARY

Each action would have a consumable openapi definition and could be called directly instead of generic execution API

ISSUE TYPE

Pick one below and delete the rest:

• Feature Idea

STACKSTORM VERSION

N/A

OS / ENVIRONMENT / INSTALL METHOD

N/A

STEPS TO REPRODUCE

This makes exposure of stackstorm actions easier for external systems. Right now, in my case, to expose meaningful northbound APIs on WSO2 based on southbound stackstorm actions through the generic execution API, I need to perform ESB level payload transformation to make the generic execution call on Stackstorm REST API.

Also makes service (action) descovery a lot easier. Right now we need to discover the yaml action metadata, turn into an API definition and deploy the API on WSO2 API Gateway. If the action would have a dedicated openapi definition, action discovery and deployment (exposure), would directly consume the openapi definition with no additional hassle and without the need of custom discovery processes.

EXPECTED RESULTS

ACTUAL RESULTS

Start by reviewing the existing generic execution API and the action YAML metadata mentioned in the issue, then trace how actions are currently discovered and exposed. The feature would be complete when each action can be called through a dedicated REST endpoint and its formal OpenAPI definition can be consumed directly by external systems.