Skip to content
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

[bitnami/mlflow] MLFlow separate settings for Auth database #25945

Open
truealex81 opened this issue May 16, 2024 · 2 comments
Open

[bitnami/mlflow] MLFlow separate settings for Auth database #25945

truealex81 opened this issue May 16, 2024 · 2 comments
Assignees
Labels
feature-request mlflow stale 15 days without activity triage Triage is needed

Comments

@truealex81
Copy link

truealex81 commented May 16, 2024

Name and Version

bitnami/mlflow 1.0.6

What is the problem this feature will solve?

Right now it is not possible to place auth database in the same postgresql database, but in different schema. For example in Azure CosmosDB for PostgreSQL is not possible to create more than one standard database on the server instance. So the only way to separate MLFlow databases is to create different schemas (for different users) and use them as a separate database.

What is the feature you are proposing to solve the problem?

Introduce separate additional parameters for auth database configuration:

externalAuthDatabase:
  host: 
  port: 
  database: 
  user: 
  password: 

What alternatives have you considered?

Right now the only alternative in my current situation is to create whole new separate Azure CosmosDB for PostgreSQL instance which is not cost efficient.

@github-actions github-actions bot added the triage Triage is needed label May 16, 2024
@javsalgar javsalgar changed the title MLFlow separate settings for Auth database [bitnami/mlflow] MLFlow separate settings for Auth database May 20, 2024
@javsalgar
Copy link
Contributor

Hi!

Thank you so much for the feature request. Would you like to submit a PR adding this support?

Copy link

github-actions bot commented Jun 5, 2024

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request mlflow stale 15 days without activity triage Triage is needed
Projects
None yet
Development

No branches or pull requests

2 participants