-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Issue 15219 - Cloud Run Jobs Launcher #21509
Conversation
feat: initial working cloud run launcher job for dagster
I’ve added two scripts that allow a user to :
To deploy the example:
Once all these changes have been applied:
You should be able to access your Dagster webserver at your public VM url, port 3000. Please let me know if you have any comments regarding the deployment process or the cloud run job launcher! |
Thank you for contributing this run launcher. Apologies for the delay on reviewing this! We're working internally on who would be the domain expert to review this and will update you once it's figured out! |
Closing this PR as some of this work will be used in: #21864 |
I've created a new Cloud Launcher, allowing to create, monitor and cancel Dagster runs on Google Cloud Run Jobs
(based on issue #15219 )
A Cloud Run Job configuration must be created in a GCP project, using a Docker image containing the user code needed to materialize the assets. The Cloud Run Job name must be specified in the instance configuration (formatted like projects/{project_id}/locations/{location}/jobs/{job_id})
I'm very new to Dagster, so I would appreciate any comments as well as guidance on the next steps for this Cloud Launcher (testing, example development...)