search

artefactory / one-click-mlflow

A tool to deploy a mostly serverless MLflow tracking server on a GCP project with one command
GNU Lesser General Public License v3.0
66 stars 21 forks source link

A new, different AppEngine service is created when doing 2+ deployments on the same project #51

Closed AlexisVLRT closed 3 years ago

AlexisVLRT commented 3 years ago

Describe the bug If a first deployment created a default AppEngine service for MLFlow, deploying again will create a new mlflow service instead of updating the first one

The main issue for the end-user is that the URL of the MLFlow server is inconsistent if you do one or multiple deployments: https://mlflow-dot-{PROJECT_ID}.ew.r.appspot.com or https://{PROJECT_ID}.ew.r.appspot.com.

To Reproduce Steps to reproduce the behavior:

  1. make one-click-mlflow -> AppEngine default is created
  2. make one-click-mlflow a second time on the same project -> AppEngine mlflow is created

Expected behavior If the first deployment created the default service, we expect it to be updated, not create a new one

Desktop (please complete the following information):

AlexisVLRT commented 3 years ago

Solved by #55