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 aim to establish a certified blueprint process for ML Commons connectors to streamline the creation, verification, and publication of custom connector blueprints. The process will allow developers to follow blueprint definitions, submit their blueprints, and have them verified through a CI workflow before being published to the official blueprint repository.
Proposal:
Blueprint Definition:
Provide a clear definition and template for users to create their own blueprints.
Define all necessary fields and structures required for a valid blueprint.
Documentation will be provided to guide users through the process.
Certification Process:
Implement a CI workflow that automatically verifies submitted blueprints.
The CI workflow will check for:
Valid structure and required fields.
Functionality and compatibility with the ML Commons plugin.
Ensure no breaking changes or invalid configurations.
Publishing to Blueprint Repository:
Once a blueprint passes the CI workflow, it will be published automatically to the blueprint repository.
A unique blueprint ID will be generated for each successful blueprint.
Connector Creation:
Users will be able to use the blueprint ID to easily create connectors within the ML Commons plugin.
This simplifies the process for leveraging external ML models or services in OpenSearch.
The text was updated successfully, but these errors were encountered:
Description:
We aim to establish a certified blueprint process for ML Commons connectors to streamline the creation, verification, and publication of custom connector blueprints. The process will allow developers to follow blueprint definitions, submit their blueprints, and have them verified through a CI workflow before being published to the official blueprint repository.
Proposal:
The text was updated successfully, but these errors were encountered: