[FEATURE] Remove user_inputs
field from template and set values directly for each workflow
#105
Labels
user_inputs
field from template and set values directly for each workflow
#105
The current use case template includes a
user_inputs
field, whose values can be used throughout the template in cases where this particular value may be used multiple times. For instance, themodel_id
orindex_name
can potentially be used in several areas.This comes with a few issues regarding parsing, and ascertaining the values of a given field such as
user_inputs.index_name
during the execution of aWorkflowStep
.To reduce complexity, it's necessary to remove the
user_inputs
section of the use case template and just set those values directly.For instance, the previous use case template to create an ingest pipeline and index (with created ingest pipeline set as the default ingest pipeline) :
Proposed use case template (without user inputs) :
The text was updated successfully, but these errors were encountered: