Added OpenAPI command coverage (#357)
This PR adds the following command groups:
## Workspace-level command groups
* `bricks alerts` - The alerts API can be used to perform CRUD operations on alerts.
* `bricks catalogs` - A catalog is the first layer of Unity Catalog’s three-level namespace.
* `bricks cluster-policies` - Cluster policy limits the ability to configure clusters based on a set of rules.
* `bricks clusters` - The Clusters API allows you to create, start, edit, list, terminate, and delete clusters.
* `bricks current-user` - This API allows retrieving information about currently authenticated user or service principal.
* `bricks dashboards` - In general, there is little need to modify dashboards using the API.
* `bricks data-sources` - This API is provided to assist you in making new query objects.
* `bricks experiments` - MLflow Experiment tracking.
* `bricks external-locations` - An external location is an object that combines a cloud storage path with a storage credential that authorizes access to the cloud storage path.
* `bricks functions` - Functions implement User-Defined Functions (UDFs) in Unity Catalog.
* `bricks git-credentials` - Registers personal access token for Databricks to do operations on behalf of the user.
* `bricks global-init-scripts` - The Global Init Scripts API enables Workspace administrators to configure global initialization scripts for their workspace.
* `bricks grants` - In Unity Catalog, data is secure by default.
* `bricks groups` - Groups simplify identity management, making it easier to assign access to Databricks Workspace, data, and other securable objects.
* `bricks instance-pools` - Instance Pools API are used to create, edit, delete and list instance pools by using ready-to-use cloud instances which reduces a cluster start and auto-scaling times.
* `bricks instance-profiles` - The Instance Profiles API allows admins to add, list, and remove instance profiles that users can launch clusters with.
* `bricks ip-access-lists` - IP Access List enables admins to configure IP access lists.
* `bricks jobs` - The Jobs API allows you to create, edit, and delete jobs.
* `bricks libraries` - The Libraries API allows you to install and uninstall libraries and get the status of libraries on a cluster.
* `bricks metastores` - A metastore is the top-level container of objects in Unity Catalog.
* `bricks model-registry` - MLflow Model Registry commands.
* `bricks permissions` - Permissions API are used to create read, write, edit, update and manage access for various users on different objects and endpoints.
* `bricks pipelines` - The Delta Live Tables API allows you to create, edit, delete, start, and view details about pipelines.
* `bricks policy-families` - View available policy families.
* `bricks providers` - Databricks Providers REST API.
* `bricks queries` - These endpoints are used for CRUD operations on query definitions.
* `bricks query-history` - Access the history of queries through SQL warehouses.
* `bricks recipient-activation` - Databricks Recipient Activation REST API.
* `bricks recipients` - Databricks Recipients REST API.
* `bricks repos` - The Repos API allows users to manage their git repos.
* `bricks schemas` - A schema (also called a database) is the second layer of Unity Catalog’s three-level namespace.
* `bricks secrets` - The Secrets API allows you to manage secrets, secret scopes, and access permissions.
* `bricks service-principals` - Identities for use with jobs, automated tools, and systems such as scripts, apps, and CI/CD platforms.
* `bricks serving-endpoints` - The Serving Endpoints API allows you to create, update, and delete model serving endpoints.
* `bricks shares` - Databricks Shares REST API.
* `bricks storage-credentials` - A storage credential represents an authentication and authorization mechanism for accessing data stored on your cloud tenant.
* `bricks table-constraints` - Primary key and foreign key constraints encode relationships between fields in tables.
* `bricks tables` - A table resides in the third layer of Unity Catalog’s three-level namespace.
* `bricks token-management` - Enables administrators to get all tokens and delete tokens for other users.
* `bricks tokens` - The Token API allows you to create, list, and revoke tokens that can be used to authenticate and access Databricks REST APIs.
* `bricks users` - User identities recognized by Databricks and represented by email addresses.
* `bricks volumes` - Volumes are a Unity Catalog (UC) capability for accessing, storing, governing, organizing and processing files.
* `bricks warehouses` - A SQL warehouse is a compute resource that lets you run SQL commands on data objects within Databricks SQL.
* `bricks workspace` - The Workspace API allows you to list, import, export, and delete notebooks and folders.
* `bricks workspace-conf` - This API allows updating known workspace settings for advanced users.
## Account-level command groups
* `bricks account billable-usage` - This API allows you to download billable usage logs for the specified account and date range.
* `bricks account budgets` - These APIs manage budget configuration including notifications for exceeding a budget for a period.
* `bricks account credentials` - These APIs manage credential configurations for this workspace.
* `bricks account custom-app-integration` - These APIs enable administrators to manage custom oauth app integrations, which is required for adding/using Custom OAuth App Integration like Tableau Cloud for Databricks in AWS cloud.
* `bricks account encryption-keys` - These APIs manage encryption key configurations for this workspace (optional).
* `bricks account groups` - Groups simplify identity management, making it easier to assign access to Databricks Account, data, and other securable objects.
* `bricks account ip-access-lists` - The Accounts IP Access List API enables account admins to configure IP access lists for access to the account console.
* `bricks account log-delivery` - These APIs manage log delivery configurations for this account.
* `bricks account metastore-assignments` - These APIs manage metastore assignments to a workspace.
* `bricks account metastores` - These APIs manage Unity Catalog metastores for an account.
* `bricks account networks` - These APIs manage network configurations for customer-managed VPCs (optional).
* `bricks account o-auth-enrollment` - These APIs enable administrators to enroll OAuth for their accounts, which is required for adding/using any OAuth published/custom application integration.
* `bricks account private-access` - These APIs manage private access settings for this account.
* `bricks account published-app-integration` - These APIs enable administrators to manage published oauth app integrations, which is required for adding/using Published OAuth App Integration like Tableau Cloud for Databricks in AWS cloud.
* `bricks account service-principals` - Identities for use with jobs, automated tools, and systems such as scripts, apps, and CI/CD platforms.
* `bricks account storage` - These APIs manage storage configurations for this workspace.
* `bricks account storage-credentials` - These APIs manage storage credentials for a particular metastore.
* `bricks account users` - User identities recognized by Databricks and represented by email addresses.
* `bricks account vpc-endpoints` - These APIs manage VPC endpoint configurations for this account.
* `bricks account workspace-assignment` - The Workspace Permission Assignment API allows you to manage workspace permissions for principals in your account.
* `bricks account workspaces` - These APIs manage workspaces for this account.
2023-04-26 11:06:16 +00:00
|
|
|
// Code generated from OpenAPI specs by Databricks SDK Generator. DO NOT EDIT.
|
|
|
|
|
|
|
|
package serving_endpoints
|
|
|
|
|
|
|
|
import (
|
|
|
|
"fmt"
|
|
|
|
"time"
|
|
|
|
|
2023-05-16 16:35:39 +00:00
|
|
|
"github.com/databricks/cli/cmd/root"
|
|
|
|
"github.com/databricks/cli/libs/cmdio"
|
|
|
|
"github.com/databricks/cli/libs/flags"
|
Added OpenAPI command coverage (#357)
This PR adds the following command groups:
## Workspace-level command groups
* `bricks alerts` - The alerts API can be used to perform CRUD operations on alerts.
* `bricks catalogs` - A catalog is the first layer of Unity Catalog’s three-level namespace.
* `bricks cluster-policies` - Cluster policy limits the ability to configure clusters based on a set of rules.
* `bricks clusters` - The Clusters API allows you to create, start, edit, list, terminate, and delete clusters.
* `bricks current-user` - This API allows retrieving information about currently authenticated user or service principal.
* `bricks dashboards` - In general, there is little need to modify dashboards using the API.
* `bricks data-sources` - This API is provided to assist you in making new query objects.
* `bricks experiments` - MLflow Experiment tracking.
* `bricks external-locations` - An external location is an object that combines a cloud storage path with a storage credential that authorizes access to the cloud storage path.
* `bricks functions` - Functions implement User-Defined Functions (UDFs) in Unity Catalog.
* `bricks git-credentials` - Registers personal access token for Databricks to do operations on behalf of the user.
* `bricks global-init-scripts` - The Global Init Scripts API enables Workspace administrators to configure global initialization scripts for their workspace.
* `bricks grants` - In Unity Catalog, data is secure by default.
* `bricks groups` - Groups simplify identity management, making it easier to assign access to Databricks Workspace, data, and other securable objects.
* `bricks instance-pools` - Instance Pools API are used to create, edit, delete and list instance pools by using ready-to-use cloud instances which reduces a cluster start and auto-scaling times.
* `bricks instance-profiles` - The Instance Profiles API allows admins to add, list, and remove instance profiles that users can launch clusters with.
* `bricks ip-access-lists` - IP Access List enables admins to configure IP access lists.
* `bricks jobs` - The Jobs API allows you to create, edit, and delete jobs.
* `bricks libraries` - The Libraries API allows you to install and uninstall libraries and get the status of libraries on a cluster.
* `bricks metastores` - A metastore is the top-level container of objects in Unity Catalog.
* `bricks model-registry` - MLflow Model Registry commands.
* `bricks permissions` - Permissions API are used to create read, write, edit, update and manage access for various users on different objects and endpoints.
* `bricks pipelines` - The Delta Live Tables API allows you to create, edit, delete, start, and view details about pipelines.
* `bricks policy-families` - View available policy families.
* `bricks providers` - Databricks Providers REST API.
* `bricks queries` - These endpoints are used for CRUD operations on query definitions.
* `bricks query-history` - Access the history of queries through SQL warehouses.
* `bricks recipient-activation` - Databricks Recipient Activation REST API.
* `bricks recipients` - Databricks Recipients REST API.
* `bricks repos` - The Repos API allows users to manage their git repos.
* `bricks schemas` - A schema (also called a database) is the second layer of Unity Catalog’s three-level namespace.
* `bricks secrets` - The Secrets API allows you to manage secrets, secret scopes, and access permissions.
* `bricks service-principals` - Identities for use with jobs, automated tools, and systems such as scripts, apps, and CI/CD platforms.
* `bricks serving-endpoints` - The Serving Endpoints API allows you to create, update, and delete model serving endpoints.
* `bricks shares` - Databricks Shares REST API.
* `bricks storage-credentials` - A storage credential represents an authentication and authorization mechanism for accessing data stored on your cloud tenant.
* `bricks table-constraints` - Primary key and foreign key constraints encode relationships between fields in tables.
* `bricks tables` - A table resides in the third layer of Unity Catalog’s three-level namespace.
* `bricks token-management` - Enables administrators to get all tokens and delete tokens for other users.
* `bricks tokens` - The Token API allows you to create, list, and revoke tokens that can be used to authenticate and access Databricks REST APIs.
* `bricks users` - User identities recognized by Databricks and represented by email addresses.
* `bricks volumes` - Volumes are a Unity Catalog (UC) capability for accessing, storing, governing, organizing and processing files.
* `bricks warehouses` - A SQL warehouse is a compute resource that lets you run SQL commands on data objects within Databricks SQL.
* `bricks workspace` - The Workspace API allows you to list, import, export, and delete notebooks and folders.
* `bricks workspace-conf` - This API allows updating known workspace settings for advanced users.
## Account-level command groups
* `bricks account billable-usage` - This API allows you to download billable usage logs for the specified account and date range.
* `bricks account budgets` - These APIs manage budget configuration including notifications for exceeding a budget for a period.
* `bricks account credentials` - These APIs manage credential configurations for this workspace.
* `bricks account custom-app-integration` - These APIs enable administrators to manage custom oauth app integrations, which is required for adding/using Custom OAuth App Integration like Tableau Cloud for Databricks in AWS cloud.
* `bricks account encryption-keys` - These APIs manage encryption key configurations for this workspace (optional).
* `bricks account groups` - Groups simplify identity management, making it easier to assign access to Databricks Account, data, and other securable objects.
* `bricks account ip-access-lists` - The Accounts IP Access List API enables account admins to configure IP access lists for access to the account console.
* `bricks account log-delivery` - These APIs manage log delivery configurations for this account.
* `bricks account metastore-assignments` - These APIs manage metastore assignments to a workspace.
* `bricks account metastores` - These APIs manage Unity Catalog metastores for an account.
* `bricks account networks` - These APIs manage network configurations for customer-managed VPCs (optional).
* `bricks account o-auth-enrollment` - These APIs enable administrators to enroll OAuth for their accounts, which is required for adding/using any OAuth published/custom application integration.
* `bricks account private-access` - These APIs manage private access settings for this account.
* `bricks account published-app-integration` - These APIs enable administrators to manage published oauth app integrations, which is required for adding/using Published OAuth App Integration like Tableau Cloud for Databricks in AWS cloud.
* `bricks account service-principals` - Identities for use with jobs, automated tools, and systems such as scripts, apps, and CI/CD platforms.
* `bricks account storage` - These APIs manage storage configurations for this workspace.
* `bricks account storage-credentials` - These APIs manage storage credentials for a particular metastore.
* `bricks account users` - User identities recognized by Databricks and represented by email addresses.
* `bricks account vpc-endpoints` - These APIs manage VPC endpoint configurations for this account.
* `bricks account workspace-assignment` - The Workspace Permission Assignment API allows you to manage workspace permissions for principals in your account.
* `bricks account workspaces` - These APIs manage workspaces for this account.
2023-04-26 11:06:16 +00:00
|
|
|
"github.com/databricks/databricks-sdk-go/retries"
|
|
|
|
"github.com/databricks/databricks-sdk-go/service/serving"
|
|
|
|
"github.com/spf13/cobra"
|
|
|
|
)
|
|
|
|
|
|
|
|
var Cmd = &cobra.Command{
|
|
|
|
Use: "serving-endpoints",
|
|
|
|
Short: `The Serving Endpoints API allows you to create, update, and delete model serving endpoints.`,
|
|
|
|
Long: `The Serving Endpoints API allows you to create, update, and delete model
|
|
|
|
serving endpoints.
|
|
|
|
|
|
|
|
You can use a serving endpoint to serve models from the Databricks Model
|
|
|
|
Registry. Endpoints expose the underlying models as scalable REST API
|
|
|
|
endpoints using serverless compute. This means the endpoints and associated
|
|
|
|
compute resources are fully managed by Databricks and will not appear in your
|
|
|
|
cloud account. A serving endpoint can consist of one or more MLflow models
|
|
|
|
from the Databricks Model Registry, called served models. A serving endpoint
|
|
|
|
can have at most ten served models. You can configure traffic settings to
|
|
|
|
define how requests should be routed to your served models behind an endpoint.
|
|
|
|
Additionally, you can configure the scale of resources that should be applied
|
|
|
|
to each served model.`,
|
|
|
|
}
|
|
|
|
|
|
|
|
// start build-logs command
|
|
|
|
|
|
|
|
var buildLogsReq serving.BuildLogsRequest
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(buildLogsCmd)
|
|
|
|
// TODO: short flags
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var buildLogsCmd = &cobra.Command{
|
|
|
|
Use: "build-logs NAME SERVED_MODEL_NAME",
|
|
|
|
Short: `Retrieve the logs associated with building the model's environment for a given serving endpoint's served model.`,
|
|
|
|
Long: `Retrieve the logs associated with building the model's environment for a given
|
|
|
|
serving endpoint's served model.
|
|
|
|
|
|
|
|
Retrieves the build logs associated with the provided served model.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
Args: cobra.ExactArgs(2),
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
buildLogsReq.Name = args[0]
|
|
|
|
buildLogsReq.ServedModelName = args[1]
|
|
|
|
|
|
|
|
response, err := w.ServingEndpoints.BuildLogs(ctx, buildLogsReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, response)
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// start create command
|
|
|
|
|
|
|
|
var createReq serving.CreateServingEndpoint
|
|
|
|
var createJson flags.JsonFlag
|
|
|
|
var createSkipWait bool
|
|
|
|
var createTimeout time.Duration
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(createCmd)
|
|
|
|
|
|
|
|
createCmd.Flags().BoolVar(&createSkipWait, "no-wait", createSkipWait, `do not wait to reach NOT_UPDATING state`)
|
|
|
|
createCmd.Flags().DurationVar(&createTimeout, "timeout", 20*time.Minute, `maximum amount of time to reach NOT_UPDATING state`)
|
|
|
|
// TODO: short flags
|
|
|
|
createCmd.Flags().Var(&createJson, "json", `either inline JSON string or @path/to/file.json with request body`)
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var createCmd = &cobra.Command{
|
|
|
|
Use: "create",
|
|
|
|
Short: `Create a new serving endpoint.`,
|
|
|
|
Long: `Create a new serving endpoint.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
err = createJson.Unmarshal(&createReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
createReq.Name = args[0]
|
|
|
|
_, err = fmt.Sscan(args[1], &createReq.Config)
|
|
|
|
if err != nil {
|
|
|
|
return fmt.Errorf("invalid CONFIG: %s", args[1])
|
|
|
|
}
|
|
|
|
|
|
|
|
if createSkipWait {
|
|
|
|
response, err := w.ServingEndpoints.Create(ctx, createReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, response)
|
|
|
|
}
|
|
|
|
spinner := cmdio.Spinner(ctx)
|
|
|
|
info, err := w.ServingEndpoints.CreateAndWait(ctx, createReq,
|
|
|
|
retries.Timeout[serving.ServingEndpointDetailed](createTimeout),
|
|
|
|
func(i *retries.Info[serving.ServingEndpointDetailed]) {
|
|
|
|
if i.Info == nil {
|
|
|
|
return
|
|
|
|
}
|
|
|
|
status := i.Info.State.ConfigUpdate
|
|
|
|
statusMessage := fmt.Sprintf("current status: %s", status)
|
|
|
|
spinner <- statusMessage
|
|
|
|
})
|
|
|
|
close(spinner)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, info)
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// start delete command
|
|
|
|
|
|
|
|
var deleteReq serving.DeleteServingEndpointRequest
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(deleteCmd)
|
|
|
|
// TODO: short flags
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var deleteCmd = &cobra.Command{
|
|
|
|
Use: "delete NAME",
|
|
|
|
Short: `Delete a serving endpoint.`,
|
|
|
|
Long: `Delete a serving endpoint.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
Args: cobra.ExactArgs(1),
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
deleteReq.Name = args[0]
|
|
|
|
|
|
|
|
err = w.ServingEndpoints.Delete(ctx, deleteReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// start export-metrics command
|
|
|
|
|
|
|
|
var exportMetricsReq serving.ExportMetricsRequest
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(exportMetricsCmd)
|
|
|
|
// TODO: short flags
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var exportMetricsCmd = &cobra.Command{
|
|
|
|
Use: "export-metrics NAME",
|
|
|
|
Short: `Retrieve the metrics corresponding to a serving endpoint for the current time in Prometheus or OpenMetrics exposition format.`,
|
|
|
|
Long: `Retrieve the metrics corresponding to a serving endpoint for the current time
|
|
|
|
in Prometheus or OpenMetrics exposition format.
|
|
|
|
|
|
|
|
Retrieves the metrics associated with the provided serving endpoint in either
|
|
|
|
Prometheus or OpenMetrics exposition format.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
Args: cobra.ExactArgs(1),
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
exportMetricsReq.Name = args[0]
|
|
|
|
|
|
|
|
err = w.ServingEndpoints.ExportMetrics(ctx, exportMetricsReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// start get command
|
|
|
|
|
|
|
|
var getReq serving.GetServingEndpointRequest
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(getCmd)
|
|
|
|
// TODO: short flags
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var getCmd = &cobra.Command{
|
|
|
|
Use: "get NAME",
|
|
|
|
Short: `Get a single serving endpoint.`,
|
|
|
|
Long: `Get a single serving endpoint.
|
|
|
|
|
|
|
|
Retrieves the details for a single serving endpoint.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
Args: cobra.ExactArgs(1),
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
getReq.Name = args[0]
|
|
|
|
|
|
|
|
response, err := w.ServingEndpoints.Get(ctx, getReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, response)
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// start list command
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(listCmd)
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var listCmd = &cobra.Command{
|
|
|
|
Use: "list",
|
|
|
|
Short: `Retrieve all serving endpoints.`,
|
|
|
|
Long: `Retrieve all serving endpoints.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
response, err := w.ServingEndpoints.List(ctx)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, response)
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// start logs command
|
|
|
|
|
|
|
|
var logsReq serving.LogsRequest
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(logsCmd)
|
|
|
|
// TODO: short flags
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var logsCmd = &cobra.Command{
|
|
|
|
Use: "logs NAME SERVED_MODEL_NAME",
|
|
|
|
Short: `Retrieve the most recent log lines associated with a given serving endpoint's served model.`,
|
|
|
|
Long: `Retrieve the most recent log lines associated with a given serving endpoint's
|
|
|
|
served model.
|
|
|
|
|
|
|
|
Retrieves the service logs associated with the provided served model.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
Args: cobra.ExactArgs(2),
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
logsReq.Name = args[0]
|
|
|
|
logsReq.ServedModelName = args[1]
|
|
|
|
|
|
|
|
response, err := w.ServingEndpoints.Logs(ctx, logsReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, response)
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// start query command
|
|
|
|
|
|
|
|
var queryReq serving.QueryRequest
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(queryCmd)
|
|
|
|
// TODO: short flags
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var queryCmd = &cobra.Command{
|
|
|
|
Use: "query NAME",
|
|
|
|
Short: `Query a serving endpoint with provided model input.`,
|
|
|
|
Long: `Query a serving endpoint with provided model input.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
Args: cobra.ExactArgs(1),
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
queryReq.Name = args[0]
|
|
|
|
|
|
|
|
response, err := w.ServingEndpoints.Query(ctx, queryReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, response)
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// start update-config command
|
|
|
|
|
|
|
|
var updateConfigReq serving.EndpointCoreConfigInput
|
|
|
|
var updateConfigJson flags.JsonFlag
|
|
|
|
var updateConfigSkipWait bool
|
|
|
|
var updateConfigTimeout time.Duration
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
Cmd.AddCommand(updateConfigCmd)
|
|
|
|
|
|
|
|
updateConfigCmd.Flags().BoolVar(&updateConfigSkipWait, "no-wait", updateConfigSkipWait, `do not wait to reach NOT_UPDATING state`)
|
|
|
|
updateConfigCmd.Flags().DurationVar(&updateConfigTimeout, "timeout", 20*time.Minute, `maximum amount of time to reach NOT_UPDATING state`)
|
|
|
|
// TODO: short flags
|
|
|
|
updateConfigCmd.Flags().Var(&updateConfigJson, "json", `either inline JSON string or @path/to/file.json with request body`)
|
|
|
|
|
|
|
|
// TODO: complex arg: traffic_config
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
var updateConfigCmd = &cobra.Command{
|
|
|
|
Use: "update-config",
|
|
|
|
Short: `Update a serving endpoint with a new config.`,
|
|
|
|
Long: `Update a serving endpoint with a new config.
|
|
|
|
|
|
|
|
Updates any combination of the serving endpoint's served models, the compute
|
|
|
|
configuration of those served models, and the endpoint's traffic config. An
|
|
|
|
endpoint that already has an update in progress can not be updated until the
|
|
|
|
current update completes or fails.`,
|
|
|
|
|
|
|
|
Annotations: map[string]string{},
|
|
|
|
PreRunE: root.MustWorkspaceClient,
|
|
|
|
RunE: func(cmd *cobra.Command, args []string) (err error) {
|
|
|
|
ctx := cmd.Context()
|
|
|
|
w := root.WorkspaceClient(ctx)
|
|
|
|
err = updateConfigJson.Unmarshal(&updateConfigReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
_, err = fmt.Sscan(args[0], &updateConfigReq.ServedModels)
|
|
|
|
if err != nil {
|
|
|
|
return fmt.Errorf("invalid SERVED_MODELS: %s", args[0])
|
|
|
|
}
|
|
|
|
updateConfigReq.Name = args[1]
|
|
|
|
|
|
|
|
if updateConfigSkipWait {
|
|
|
|
response, err := w.ServingEndpoints.UpdateConfig(ctx, updateConfigReq)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, response)
|
|
|
|
}
|
|
|
|
spinner := cmdio.Spinner(ctx)
|
|
|
|
info, err := w.ServingEndpoints.UpdateConfigAndWait(ctx, updateConfigReq,
|
|
|
|
retries.Timeout[serving.ServingEndpointDetailed](updateConfigTimeout),
|
|
|
|
func(i *retries.Info[serving.ServingEndpointDetailed]) {
|
|
|
|
if i.Info == nil {
|
|
|
|
return
|
|
|
|
}
|
|
|
|
status := i.Info.State.ConfigUpdate
|
|
|
|
statusMessage := fmt.Sprintf("current status: %s", status)
|
|
|
|
spinner <- statusMessage
|
|
|
|
})
|
|
|
|
close(spinner)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return cmdio.Render(ctx, info)
|
|
|
|
},
|
|
|
|
}
|
|
|
|
|
|
|
|
// end service ServingEndpoints
|