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

Add base_image support to the serverless_prod_deploy action #193

Closed
wants to merge 1 commit into from

Conversation

gibsondan
Copy link
Member

Summary:
Allows you to set build:base_image to vary the base image per code location.

Would like to port this to the new "dagster-cloud ci" commands as well.

Test Plan:
Build a release branch and test a build with and without the base_image set, in both a dagster_cloud.yaml file and in the action itself.

Summary:
Allows you to set build:base_image to vary the base image per code location.

Would like to port this to the new "dagster-cloud ci" commands as well.

Test Plan:
Build a release branch and test a build with and without the base_image set, in both a dagster_cloud.yaml file and in the action itself.
@gibsondan gibsondan requested a review from shalabhc August 6, 2024 19:35
Copy link

github-actions bot commented Aug 6, 2024

Your pull request is automatically being deployed to Dagster Cloud.

Location Status Link Updated
from_gh_action View in Cloud Dec 27, 2024 at 03:42 PM (UTC)

Copy link
Contributor

@shalabhc shalabhc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This only affects the old workflow only for docker deploys and only in github. Adding a cicd specific feature to dagster_cloud.yaml doesn't seem right. For instance, there is no dagster-cloud cli command that will be affected by this parameter.

Should we just support this in the new workflow: https://github.com/dagster-io/dagster-cloud-action/blob/380badc507e760c569c6c1a3c914ddbf3b5cff81/github/serverless/dagster-plus-deploy.yml

@gibsondan gibsondan closed this Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants