-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Add an API to return validation parameters #364
Labels
Comments
dbwiddis
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
untriaged
v2.12.0
labels
Jan 5, 2024
Request: Response:
|
Should we remove the create index and create ingest pipeline from the JSON? |
We should. Let me push the change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem?
Users do not have an easy way to validate workflow steps, particularly in understanding what parameters are part of the output (e.g.,
model_id
) and which inputs are required vs. optional (other than by laboriously visiting original API docs). We should allow users to easily identify these requirements via API.In addition, the planned front-end will need access to this same information in order to enable real-time validation in the drag-and-drop interface.
What solution would you like?
Create a new REST API to return content equivalent to the workflow-steps.json file.
Allow an optional parameter for the workflow step type which returns only the content of that portion of the file.
What alternatives have you considered?
Do you have any additional context?
We already parse the contents of this file into a
WorkflowValidator
class, which internally contains aMap<String, WorkflowStepValidator>
.toXContent()
methods.WorkflowStepValidator
map. We can then remove theparse
methods and all the complexity with exceptions that they bring.The text was updated successfully, but these errors were encountered: