MLflow Webhook
laktory.models.resources.databricks.MLflowWebhook
¤
Bases: MlflowWebhookBase
MLflow Webhook
Examples:
import io
from laktory import models
webhook_yaml = '''
events:
- TRANSITION_REQUEST_CREATED
description: Databricks Job webhook trigger
status: ACTIVE
job_spec:
job_id: some_id
workspace_url: https://adb-1234567890.azuredatabricks.net
access_token: some_token
'''
webhook = models.resources.databricks.MLflowWebhook.model_validate_yaml(
io.StringIO(webhook_yaml)
)
References
| BASE | DESCRIPTION |
|---|---|
description
|
Optional description of the MLflow webhook
TYPE:
|
events
|
The list of events that will trigger execution of Databricks job or POSTing to an URL, for example,
TYPE:
|
http_url_spec
|
TYPE:
|
job_spec
|
TYPE:
|
model_name
|
Name of MLflow model for which webhook will be created. If the model name is not specified, a registry-wide webhook is created that listens for the specified events across all versions of all registered models
TYPE:
|
status
|
Optional status of webhook. Possible values are
TYPE:
|
laktory.models.resources.databricks.mlflowwebhook.MlflowWebhookHttpUrlSpec
¤
Bases: BaseModel
| PARAMETER | DESCRIPTION |
|---|---|
authorization
|
Value of the authorization header that should be sent in the request sent by the wehbook. It should be of the form
TYPE:
|
enable_ssl_verification
|
Enable/disable SSL certificate validation. Default is
TYPE:
|
secret
|
Shared secret required for HMAC encoding payload. The HMAC-encoded payload will be sent in the header as
TYPE:
|
url
|
External HTTPS URL called on event trigger (by using a POST request). Structure of payload depends on the event type, refer to documentation for more details
TYPE:
|
laktory.models.resources.databricks.mlflowwebhook.MlflowWebhookJobSpec
¤
Bases: BaseModel
| PARAMETER | DESCRIPTION |
|---|---|
access_token
|
The personal access token used to authorize webhook's job runs
TYPE:
|
job_id
|
ID of the Databricks job that the webhook runs
TYPE:
|
workspace_url
|
URL of the workspace containing the job that this webhook runs. If not specified, the job’s workspace URL is assumed to be the same as the workspace where the webhook is created
TYPE:
|