Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / artefactory/one-click-mlflow issues and pull requests
#34 - Fix/read from gcs
Pull Request -
State: closed - Opened by griseau over 4 years ago
#34 - Fix/read from gcs
Pull Request -
State: closed - Opened by griseau over 4 years ago
#33 - Add terraform validate in CI
Issue -
State: closed - Opened by griseau over 4 years ago
- 1 comment
Labels: TODO before 1.0
#33 - Add terraform validate in CI
Issue -
State: closed - Opened by griseau over 4 years ago
- 1 comment
Labels: TODO before 1.0
#32 - Feature/prep release
Pull Request -
State: closed - Opened by griseau over 4 years ago
#32 - Feature/prep release
Pull Request -
State: closed - Opened by griseau over 4 years ago
#31 - Remove dependency to google cloud sdk beta in Dockerfile
Issue -
State: closed - Opened by griseau over 4 years ago
#31 - Remove dependency to google cloud sdk beta in Dockerfile
Issue -
State: closed - Opened by griseau over 4 years ago
#30 - Fix/output file name
Pull Request -
State: closed - Opened by griseau over 4 years ago
#30 - Fix/output file name
Pull Request -
State: closed - Opened by griseau over 4 years ago
#29 - Update issue templates
Pull Request -
State: closed - Opened by griseau over 4 years ago
#29 - Update issue templates
Pull Request -
State: closed - Opened by griseau over 4 years ago
#28 - As a user, I want to be able to migrate experiments from another MLflow deployment to one managed by one-click-mlflow
Issue -
State: open - Opened by griseau over 4 years ago
- 1 comment
Labels: enhancement, to refine
#28 - As a user, I want to be able to migrate experiments from another MLflow deployment to one managed by one-click-mlflow
Issue -
State: open - Opened by griseau over 4 years ago
- 1 comment
Labels: enhancement, to refine
#27 - Technical story: CI tests the nominal deployment scenario of one-click-mlflow. Triggered by PRs on Github.
Issue -
State: open - Opened by AlexisVLRT over 4 years ago
Labels: TODO before 1.0
#27 - Technical story: CI tests the nominal deployment scenario of one-click-mlflow. Triggered by PRs on Github.
Issue -
State: open - Opened by AlexisVLRT over 4 years ago
Labels: TODO before 1.0
#26 - One-click-mlflow App Engine service name should not be "default", however the first service deployed on a GCP project has to be named "default". Find a workaround.
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 2 comments
Labels: good first issue, TODO before 1.0
#26 - One-click-mlflow App Engine service name should not be "default", however the first service deployed on a GCP project has to be named "default". Find a workaround.
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 2 comments
Labels: good first issue, TODO before 1.0
#25 - Existing brands or App Engine applications should automatically be imported in the TFState
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 2 comments
Labels: good first issue, user experience, TODO before 1.0
#25 - Existing brands or App Engine applications should automatically be imported in the TFState
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 2 comments
Labels: good first issue, user experience, TODO before 1.0
#24 - QoL changes
Pull Request -
State: closed - Opened by AlexisVLRT over 4 years ago
#24 - QoL changes
Pull Request -
State: closed - Opened by AlexisVLRT over 4 years ago
#23 - Have an `Editor` role deployment option
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 1 comment
Labels: good first issue, user experience
#23 - Have an `Editor` role deployment option
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 1 comment
Labels: good first issue, user experience
#22 - Delete unnecessary files
Pull Request -
State: closed - Opened by griseau over 4 years ago
#22 - Delete unnecessary files
Pull Request -
State: closed - Opened by griseau over 4 years ago
#21 - 0.0.2
Pull Request -
State: closed - Opened by griseau over 4 years ago
#21 - 0.0.2
Pull Request -
State: closed - Opened by griseau over 4 years ago
#20 - Technical story: build docker image on Cloud Build instead of locally
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 1 comment
Labels: good first issue
#20 - Technical story: build docker image on Cloud Build instead of locally
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 1 comment
Labels: good first issue
#19 - As a user, I want to be able to use one-click-mlflow on AWS
Issue -
State: open - Opened by AlexisVLRT over 4 years ago
Labels: enhancement, In the roadmap, to refine
#19 - As a user, I want to be able to use one-click-mlflow on AWS
Issue -
State: open - Opened by AlexisVLRT over 4 years ago
Labels: enhancement, In the roadmap, to refine
#18 - Create Azure version
Issue -
State: closed - Opened by griseau over 4 years ago
Labels: enhancement
#18 - Create Azure version
Issue -
State: closed - Opened by griseau over 4 years ago
Labels: enhancement
#17 - 0.0.1
Pull Request -
State: closed - Opened by griseau over 4 years ago
#17 - 0.0.1
Pull Request -
State: closed - Opened by griseau over 4 years ago
#16 - Feature/app engine
Pull Request -
State: closed - Opened by AlexisVLRT over 4 years ago
#16 - Feature/app engine
Pull Request -
State: closed - Opened by AlexisVLRT over 4 years ago
#15 - Landing page of the web app is broken and fails to redirect to the consent screen when not authenticated
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 1 comment
Labels: good first issue, user experience
#14 - Application can not be destroyed by terraform but are still removed from the TFstate, causing crashes when re-deploying after destroying.
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 2 comments
Labels: bug
#13 - Brands can not be destroyed by terraform but are still removed from the TFstate, causing crashes when re-deploying after destroying.
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 2 comments
Labels: bug
#12 - Change cloud run to app engine
Issue -
State: closed - Opened by griseau over 4 years ago
#11 - Create a helper for MLFLOW_TRACKING_TOKEN reception and use
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
Labels: P1
#10 - V1 avec Terraform
Pull Request -
State: closed - Opened by griseau over 4 years ago
#9 - add: dockerfile
Pull Request -
State: closed - Opened by AlexisVLRT over 4 years ago
#8 - As a user, I want to be able to use one-click-mlflow to deploy and serve models
Issue -
State: open - Opened by AlexisVLRT over 4 years ago
Labels: enhancement
#7 - A docker image for the tracking server
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
Labels: P1
#6 - A makefile to get the SACC, build the image, and start the terraform
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
#5 - Setup IAP for end user access to the tracking server
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
Labels: P1
#4 - As a user, I do not want one-click-mflow to run if I am not Owner of the GCP project
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
- 1 comment
Labels: good first issue, user experience, TODO before 1.0
#3 - Setup access from code to push logs to the tracking server
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
#2 - View about migrating from local files to the CloudSQL backend
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
#1 - Write the terraform stuff
Issue -
State: closed - Opened by AlexisVLRT over 4 years ago
Labels: P1