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

[FR] Discard DB IRIS_TASKS and use main POSTGRES_DB or at least replace the hard coded db name with a configurable one #544

Open
StaSys846 opened this issue Jul 23, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@StaSys846
Copy link

Please ensure your feature request is not already on the roadmap or associated with an issue. This can be checked here.

Is your feature request related to a problem? Please describe.
Currently IRIS uses two databases: A DB with configurable name via POSTGRES_DB env var and a second hard coded DB with the name "IRIS_TASKS" (defined in iris post_init source code). When deploying multiple IRIS instances (e.g dev/prod) on a single postgres cluster (e.g. AWS RDS) both IRIS instances interfere and want to use the same hard coded DB (each instance needs its own IRIS_TASKS db).

Describe the solution you'd like
Either use additional tables (used in the IRIS_TASKS db) in the already existing main DB with the name defined by POSTGRES_DB env var (preferred) or use a configurable name for the IRIS_TASKS db (e.g. by an additional env var).

Additional context
Currently unclear why a second DB is needed at all. And when inherently needed, make the DB name customizable.

@StaSys846 StaSys846 added the enhancement New feature or request label Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant