You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WDK currently uses a watched directory as a basis for managing workflows. One would need access to that directory to deploy, edit or delete workflows. This can be challenging either in an enterprise setting or when integrations to other systems are required, e.g. to build controls around who can view or modify workflows.
Potential Solutions:
Since WDK already contains an embedded web server for receiving webhooks, it can be extended with some endpoints for managing workflows using the following actions:
Validate a SWADL payload
Deploy a new workflow
Update an existing workflow
Delete an existing workflow
These endpoints should be disabled by default and enabled in Spring configuration, along with a configurable security token to prevent unauthorised calls.
The text was updated successfully, but these errors were encountered:
Feature Request
Description of Problem:
WDK currently uses a watched directory as a basis for managing workflows. One would need access to that directory to deploy, edit or delete workflows. This can be challenging either in an enterprise setting or when integrations to other systems are required, e.g. to build controls around who can view or modify workflows.
Potential Solutions:
Since WDK already contains an embedded web server for receiving webhooks, it can be extended with some endpoints for managing workflows using the following actions:
These endpoints should be disabled by default and enabled in Spring configuration, along with a configurable security token to prevent unauthorised calls.
The text was updated successfully, but these errors were encountered: