-
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
[docs] - Update Dagster+ CI/CD files into single deploy.yml #23035
Conversation
<a href="/dagster-plus/managing-deployments/branch-deployments"> | ||
Branch Deployments | ||
</a>{" "} | ||
(For Dagster+ accounts created after [TODO]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace with date when we have it
</li> | ||
</ul> | ||
Defines the steps required to use Branch Deployments.{" "} | ||
<strong>For Dagster+ accounts created after [TODO]</strong>, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace with date when we have it
<TabItem name="Using GitHub Actions"> | ||
|
||
<Note> | ||
<strong>Heads up!</strong> If your Dagster+ account was created before [TODO], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace with date when we have it
@@ -408,11 +414,15 @@ height={537} | |||
<TabGroup> | |||
<TabItem name="Using GitHub Actions"> | |||
|
|||
Finally, we can add a step to our `branch_deployments.yml` file that queues a run of our `drop_prod_clone` job: | |||
<Note> | |||
<strong>Heads up!</strong> If your Dagster+ account was created before [TODO], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace with date when we have it
@@ -220,7 +218,7 @@ The last step is to update the [CI/CD files](/dagster-plus/references/ci-cd-file | |||
|
|||
5. Save the changes. | |||
|
|||
6. Open the `branch_deployments.yml` file and repeat steps 3 - 5. | |||
6. **If your Dagster+ account was created before \[TODO]**, open the `branch_deployments.yml` file and repeat steps 3 - 5. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace with date when we have it
@@ -32,6 +32,8 @@ When Dagster deploys the code, a few things happen: | |||
- `.github/workflows/deploy.yml` - This file sets up Continuous Deployment (CD) for the repository. We won’t talk through all the steps here, but a high-level summary is that every time a change is made to the `main` branch of your repository, this GitHub Action will build your Dagster project and deploy it to Dagster+. | |||
- `.github/workflows/branch_deployments.yml` - This file enables the use of [Branch Deployments](https://docs.dagster.io/dagster-cloud/managing-deployments/branch-deployments), a Dagster+ feature that automatically creates staging environments for your Dagster code with every pull request. We won’t work with Branch Deployments during this lesson, but we highly recommend trying them out! | |||
|
|||
**Note**: This file is only created if your Dagster+ account was created before [TODO]. If your account was created on or after this date, the `branch_deployments.yml` file will be consolidated into `deploy.yml`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace with date when we have it
Deploy preview for dagster-university ready! ✅ Preview Built with commit 0e97f90. |
Summary & Motivation
This PR updates the docs to reflect the changes in dagster-io/dagster-cloud-action#187 and dagster-io/dagster-cloud-action#188. Serverless deployments will now have a single
deploy.yml
for GitHub Actions, matching Hybrid.How I Tested These Changes