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

Guidelines for bootstrapping a database resource #25945

Open
davidonlaptop opened this issue Nov 15, 2024 · 1 comment
Open

Guidelines for bootstrapping a database resource #25945

davidonlaptop opened this issue Nov 15, 2024 · 1 comment
Labels
area: docs Related to documentation in general

Comments

@davidonlaptop
Copy link

What's the issue or suggestion?

Say you're managing postgres or ElasticSearch as dagster resources, and create all the tables as assets, is there recommendations on how to manage initializations instructions such as schema creation, user/role creations, etc. ?

Typically with rdbms you typically would do that as a database migration, but since mostly everything is created in dagster I thought there might be a best practice on where to do those operations?

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

@davidonlaptop davidonlaptop added the area: docs Related to documentation in general label Nov 15, 2024
@davidonlaptop
Copy link
Author

So far I have been using duckdb_init() and elasticsearch_init() assets, as dependencies.

This approach works, but just thought that resource initialization might be an interesting use case for the dagster community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Related to documentation in general
Projects
None yet
Development

No branches or pull requests

1 participant