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.

Sign up for GitHub

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

Jump to bottom

Add ability to do multiple gleanerio and tenant configs #108

Open

valentinedwv opened this issue Jun 7, 2024 · 0 comments

valentinedwv commented Jun 7, 2024 •

edited

Loading

This will be dependent upon #106

It would be nice to have a fully centralized service when multiple config files could be

Option 1 is to run multiple workflows. Need to ensure that a project variable gets sent all the way through, and that a ingest code container could be configured with some parameters that are different for each workflow
think this might help: https://docs.dagster.io/_apidocs/cli#dagster-api-grpc
or bit of a config pain, but each community might have an compose-override with a variable to namespace it.
see https://docs.docker.com/compose/compose-file/10-fragments/#example-4

Long term option we have a higher level config that just manages everything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment