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
We currently display the associated resources created from a workflow. But, it would be even more helpful to drill down further into these resources, and view their individual configurations. For example, if a workflow creates an ingest pipeline, I may want to look at the pipeline config in a standalone way. Or, view some created index's generated mappings, or default settings. This can help in overall visibility, and let users decide if they want to override some defaults, or pass around those individual resource configs for deeper testing, etc.
The resources are visible in 2 places. Once on the workflow list page in the right-side flyout, and once under the "Resources" tab in the Tools panel in the workflow detail page:
Ideally, we have some mechanism to click on those resources, or have a button somewhere, to pull up the resource details. Since we know the resource type and resource ID, we can execute the corresponding GET call to fetch such details. A few APIs may need to be added on the frontend to support this:
We currently display the associated resources created from a workflow. But, it would be even more helpful to drill down further into these resources, and view their individual configurations. For example, if a workflow creates an ingest pipeline, I may want to look at the pipeline config in a standalone way. Or, view some created index's generated mappings, or default settings. This can help in overall visibility, and let users decide if they want to override some defaults, or pass around those individual resource configs for deeper testing, etc.
The resources are visible in 2 places. Once on the workflow list page in the right-side flyout, and once under the "Resources" tab in the Tools panel in the workflow detail page:
Ideally, we have some mechanism to click on those resources, or have a button somewhere, to pull up the resource details. Since we know the resource type and resource ID, we can execute the corresponding
GET
call to fetch such details. A few APIs may need to be added on the frontend to support this:The text was updated successfully, but these errors were encountered: