-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[BUG] Tags are not added to sagemaker endpoints during deployment. #9159
Comments
@clarkh-ncino Thanks for reporting the issue! It looks like we use |
https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_Tag.html
Both model and endpoint are taggable. @clarkh-ncino Would it makes sense to apply the same tag on both model and endpoint? |
@harupy Yes, I believe that is the expected behavior. |
@clarkh-ncino Sounds good. Can you file a RP? |
@harupy Just to clarify, do you mean pull request (PR)? If so, absolutely. Can share it out in the near future. |
yes, I meant pull request. |
@mlflow/mlflow-team Please assign a maintainer and start triaging this issue. |
#9310) Signed-off-by: Clark Hollar <[email protected]>
…ow#9159 (mlflow#9310) Signed-off-by: Clark Hollar <[email protected]>
…ow#9159 (mlflow#9310) Signed-off-by: Clark Hollar <[email protected]>
Issues Policy acknowledgement
Willingness to contribute
Yes. I would be willing to contribute a fix for this bug with guidance from the MLflow community.
MLflow version
System information
Describe the problem
When deploying a model to sagemaker, tags passed to the _create_sagemaker_endpoint and _update_sagemaker_endpoint functions are not added to endpoints as expected. Tags for endpoints are being set to an empty array here.
Tracking information
Code to reproduce issue
Stack trace
Other info / logs
What component(s) does this bug affect?
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/gateway
: AI Gateway service, Gateway client APIs, third-party Gateway integrationsarea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingWhat interface(s) does this bug affect?
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportWhat language(s) does this bug affect?
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesWhat integration(s) does this bug affect?
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsThe text was updated successfully, but these errors were encountered: