Skip to content

Commit

Permalink
[docs] Update URL to Definitions for project-fully-featured (#23350)
Browse files Browse the repository at this point in the history
## Summary & Motivation

This PR updates the URL to the file containing Definitions in
project-fully-featured. That was moved from #23316 to this PR to avoid
failure when running the doc tests - the file must exist before being
referenced, and it is updated in #23345.

## How I Tested These Changes

BK
  • Loading branch information
maximearmstrong authored Aug 13, 2024
1 parent 3012a29 commit 2ef4f25
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ In this example, we grouped resources (e.g., database connections, Spark session

In complex projects, we find it helpful to make resources reusable and configured with pre-defined values via <PyObject object="configured" />. This approach allows your teammates to use a pre-defined resource set or make changes to shared resources, thus enabling more efficient project development.

This pattern also helps you easily execute jobs in different environments without code changes. In this example, we dynamically defined a code location based on the deployment in [`definitions.py`](https://github.com/dagster-io/dagster/blob/master/examples/project_fully_featured/project_fully_featured/\__init\_\_.py) and can keep all code the same across testing, local development, staging, and production. Read more about our recommendations in the [Transitioning data pipelines from Development to Production](/guides/dagster/transitioning-data-pipelines-from-development-to-production) guide.
This pattern also helps you easily execute jobs in different environments without code changes. In this example, we dynamically defined a code location based on the deployment in [`definitions.py`](https://github.com/dagster-io/dagster/blob/master/examples/project_fully_featured/project_fully_featured/definitions.py) and can keep all code the same across testing, local development, staging, and production. Read more about our recommendations in the [Transitioning data pipelines from Development to Production](/guides/dagster/transitioning-data-pipelines-from-development-to-production) guide.

---

Expand Down

1 comment on commit 2ef4f25

@github-actions
Copy link

Choose a reason for hiding this comment

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

Deploy preview for dagster-docs ready!

✅ Preview
https://dagster-docs-5fgu9kzui-elementl.vercel.app
https://master.dagster.dagster-docs.io

Built with commit 2ef4f25.
This pull request is being automatically deployed with vercel-action

Please sign in to comment.