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
The user provisioning a resource is not always the same user who needs to use the resource.
For example, the user provisioning a template to create an agent (typically a back-end role) may not be the same user who needs the agent ID to query the agent (typically a front-end role).
What solution would you like?
We currently provide a status API for a specific workflow which returns created resources, for example
The directional idea is to modify the index mapping of the workflow state index such that resources created are static fields rather than dynamic, and to expose a new API to search the workflow state index using OS DSL. This is to allow for querying the workflow state index for specific term values within the objects of the array. Created resources should be changed to the following format :
Is your feature request related to a problem?
The user provisioning a resource is not always the same user who needs to use the resource.
For example, the user provisioning a template to create an agent (typically a back-end role) may not be the same user who needs the agent ID to query the agent (typically a front-end role).
What solution would you like?
We currently provide a status API for a specific workflow which returns created resources, for example
Of note, the "workflow_step_id" is a user-provided, unique id that could be used as a search term.
We need an API to search all created resources, regardless of which workflow created them, identifying a match based on the worfklow step id.
The text was updated successfully, but these errors were encountered: