Fix issues with MachineLearning::Model::Registry and add rake tasks to manage indices, pipelines, and models #114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes two issues and adds new functionality to the codebase. The first issue (#112) is related to the creation of the
MachineLearning::Model::Registry
class.It allows tracking ML model deployment in stretchy apps.
The second issue (#113) involves the addition of rake tasks to manage indices, pipelines, and models. This pull request adds several rake tasks to perform various operations such as checking the status of indices, pipelines, and ML models, registering and deploying ML models, creating and deleting indices and pipelines, and more. These rake tasks provide convenient command-line tools for managing the Elasticsearch functionality in the codebase.
The commits included in this pull request are:
Fix Create MachineLearning::Model::Registry #112 Create MachineLearning::Model::Registry
Fix Add rake tasks to manage indices, pipelines and models #113 Add rake tasks to manage indices, pipelines and models
Please review the changes and let me know if any further modifications are required.