[examples] consolidate docs_beta_snippets and docs_snippets (#28771)

## Summary & Motivation

Closes DOC-898.

Consolidates the `examples/docs_beta_snippets/` and
`examples/docs_snippets` directory for improved maintainability and
organization.

## How I Tested These Changes

## Changelog

NOCHANGELOG

Author: cmpadden

.buildkite/dagster-buildkite/dagster_buildkite/steps/packages.py

@@ -303,14 +303,6 @@ def k8s_extra_cmds(version: AvailablePythonVersion, _) -> List[str]:
         # snippets in all python versions since we are testing the core code exercised by the
         # snippets against all supported python versions.
         unsupported_python_versions=AvailablePythonVersion.get_all_except_default(),
-    ),
-    PackageSpec(
-        "examples/docs_beta_snippets",
-        # The docs_snippets test suite also installs a ton of packages in the same environment,
-        # which is liable to cause dependency collisions. It's not necessary to test all these
-        # snippets in all python versions since we are testing the core code exercised by the
-        # snippets against all supported python versions.
-        unsupported_python_versions=AvailablePythonVersion.get_all_except_default(),
         pytest_tox_factors=["all", "integrations", "docs_snapshot_test"],
         always_run_if=has_dg_or_components_changes,
     ),

.buildkite/dagster-buildkite/dagster_buildkite/utils.py

@@ -324,7 +324,7 @@ def has_dg_or_components_changes():
     return any(
         "dagster-dg" in str(path)
         or "dagster-components" in str(path)
-        or "docs_beta_snippets" in str(path)
+        or "docs_snippets" in str(path)
         for path in ChangedFiles.all
     )
 

.github/workflows/build-docs.yml

@@ -6,7 +6,6 @@ on:
       - 'release-*'
     paths:
       - docs/**
-      - examples/docs_beta_snippets/**
       - examples/docs_snippets/**
       - examples/docs_projects/**
       - examples/getting_started_etl_tutorial/**
@@ -20,7 +19,6 @@ on:
   pull_request:
     paths:
       - docs/**
-      - examples/docs_beta_snippets/**
       - examples/docs_snippets/**
       - examples/docs_projects/**
       - examples/getting_started_etl_tutorial/**

docs/CONTRIBUTING.md

@@ -250,7 +250,7 @@ Some CLI invocations may be brief enough that we don't want to include them in a
 <CliInvocationExample contents="uv add 'dagster-components[sling]'" />
 ```
 
-For more information on testing the CLI commands used in docs, see [the README in docs tests](../../examples/docs_beta_snippets/docs_beta_snippets_tests/snippet_checks/README.md).
+For more information on testing the CLI commands used in docs, see [the README in docs tests](../../examples/docs_snippets/docs_snippets_tests/snippet_checks/README.md).
 
 ### Code reference links
 

docs/Makefile

@@ -30,16 +30,16 @@ sphinx_objects_inv:
 	cp sphinx/_build/json/objects.inv static/.
 
 regenerate_cli_snippets:
-	cd ../examples/docs_beta_snippets && tox -e docs_snapshot_update && echo "\nSnippets regenerated!"
+	cd ../examples/docs_snippets && tox -e docs_snapshot_update && echo "\nSnippets regenerated!"
 
 regenerate_cli_snippets_and_screenshots:
-	cd ../examples/docs_beta_snippets && EXTRA_PARAMS='--update-screenshots' tox -e docs_snapshot_update && echo "\nSnippets regenerated!"
+	cd ../examples/docs_snippets && EXTRA_PARAMS='--update-screenshots' tox -e docs_snapshot_update && echo "\nSnippets regenerated!"
 
 regenerate_cli_snippets_and_test:
-	cd ../examples/docs_beta_snippets && tox -e docs_snapshot_update && tox -e docs_snapshot_test && echo "\nSnippets regenerated and tested!"
+	cd ../examples/docs_snippets && tox -e docs_snapshot_update && tox -e docs_snapshot_test && echo "\nSnippets regenerated and tested!"
 
 regenerate_cli_snippets_and_test_debug:
-	cd ../examples/docs_beta_snippets && rm -rf /tmp/cli_snippets && mkdir -p /tmp/cli_snippets && (DAGSTER_CLI_SNIPPET_WORKING_DIR=/tmp/cli_snippets tox -e docs_snapshot_update && DAGSTER_CLI_SNIPPET_WORKING_DIR=/tmp/cli_snippets  tox -e docs_snapshot_test && echo "\nSnippets regenerated and tested!") || (echo "Snippet regeneration failed. Please check the logs for more information. Working directory: /tmp/cli_snippets" && exit 1)
+	cd ../examples/docs_snippets && rm -rf /tmp/cli_snippets && mkdir -p /tmp/cli_snippets && (DAGSTER_CLI_SNIPPET_WORKING_DIR=/tmp/cli_snippets tox -e docs_snapshot_update && DAGSTER_CLI_SNIPPET_WORKING_DIR=/tmp/cli_snippets  tox -e docs_snapshot_test && echo "\nSnippets regenerated and tested!") || (echo "Snippet regeneration failed. Please check the logs for more information. Working directory: /tmp/cli_snippets" && exit 1)
 
 test_cli_snippets_simulate_bk:
-	docker run --platform linux/amd64 --rm -it  -v "$(DAGSTER_GIT_REPO_DIR):/dagster" --entrypoint /bin/sh dagster/buildkite-test:py3.9-2025-01-31T181043 -c 'cd /dagster/examples/docs_beta_snippets && tox -e docs_snapshot_test -- --pdb'
+	docker run --platform linux/amd64 --rm -it  -v "$(DAGSTER_GIT_REPO_DIR):/dagster" --entrypoint /bin/sh dagster/buildkite-test:py3.9-2025-01-31T181043 -c 'cd /dagster/examples/docs_snippets && tox -e docs_snapshot_test -- --pdb'

docs/README.md

@@ -8,7 +8,7 @@ This is the home of the Dagster documentation. The documentation site is built u
 
 - `./src` contains custom components, styles, themes, and layouts.
 - `./docs/` contains documentation Markdown files.
-- `/examples/docs_snippets/docs_snippets/` contains code examples for the documentation. Some code examples also live in `/examples/` and `/examples/docs_beta_snippets/docs_beta_snippets/`.
+- `/examples/docs_snippets/docs_snippets/` contains code examples for the documentation. Some code examples also live in `/examples/` and `/examples/docs_snippets/docs_snippets/`.
 
 The docs are organized into the following sections:
 

docs/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/setup.md

@@ -433,19 +433,19 @@ The units for CPU and memory resources are described [in this document](https://
 
 The default behavior in Dagster+ is to create one pod for a run. Each asset targeted by that run is executed in subprocess within the pod. Use a job tag to request resources for this pod, which in turn makes those resources available to the targeted assets.
 
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/hybrid/agents/kubernetes/resource_request_job.py" language="python" title="Request resources for a job" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/hybrid/agents/kubernetes/resource_request_job.py" language="python" title="Request resources for a job" />
 
 Another option is to launch a pod for each asset by telling Dagster to use the Kubernetes job executor. In this case, you can specify resources for each individual asset.
 
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/hybrid/agents/kubernetes/resource_request_asset.py" language="python" title="Request resources for an asset" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/hybrid/agents/kubernetes/resource_request_asset.py" language="python" title="Request resources for an asset" />
 
 </TabItem>
 
 <TabItem value="pipes" label="Resources if using kubernetes pipes">
 
 Dagster can launch and manage existing Docker images as Kubernetes jobs using the [Dagster kubernetes pipes integration](/integrations/libraries/kubernetes). To request resources for these jobs by supplying the appropriate Kubernetes pod spec.
 
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/hybrid/agents/kubernetes/resource_request_pipes.py" language="python" title="Request resources for a k8s pipes asset" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/hybrid/agents/kubernetes/resource_request_pipes.py" language="python" title="Request resources for a k8s pipes asset" />
 
 
 

docs/docs/dagster-plus/deployment/deployment-types/hybrid/local.md

@@ -41,7 +41,7 @@ Your local agent will need a token to authenticate with your Dagster+ account. T
 
 1. Create a directory to act as your Dagster home. This guide uses `~/dagster_home`, but the directory can be located wherever you want.
 2. In the new directory, create a `dagster.yaml` file with the following:
-    <CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/hybrid/agents/local_dagster.yaml" language="yaml" title="dagster.yaml" />
+    <CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/hybrid/agents/local_dagster.yaml" language="yaml" title="dagster.yaml" />
 3. In the file, fill in the following:
     - `agent_token.env` - The name of the environment variable storing the agent token you created in Step 1.
     - `deployment` - The name of the deployment associated with this instance of the agent. In the preceding example, `prod` was used as the deployment.

docs/docs/dagster-plus/deployment/deployment-types/serverless/runtime-environment.md

@@ -17,7 +17,7 @@ By default, Dagster+ Serverless will package your code as PEX files and deploys
 
 You can add dependencies by including the corresponding Python libraries in your Dagster project's `setup.py` file. These should follow [PEP 508](https://peps.python.org/pep-0508/).
 
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/example_setup.py" language="Python" title="Example setup.py" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/example_setup.py" language="Python" title="Example setup.py" />
 
 You can also use a tarball to install a dependency, such as if `pip` is unable to resolve a package using `dependency_links`. For example, `soda` and `soda-snowflake` provide tarballs that you can include in the `install_requires` section:
 
@@ -48,18 +48,18 @@ Python versions 3.9 through 3.12 are all supported for Serverless deployments. Y
 <Tabs groupId="method">
 <TabItem value="GitHub" label="GitHub">
 In your `.github/workflows/deploy.yml` file, update the `PYTHON_VERSION` environment variable with your desired Python version:
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/github_python_version.yaml" language="yaml" title="Updating the Python version in deploy.yml" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/github_python_version.yaml" language="yaml" title="Updating the Python version in deploy.yml" />
 
 </TabItem>
 <TabItem value="GitLab" label="GitLab">
 1. Open your `.gitlab-ci.yml` file. If your `.gitlab-ci.yml` contains an `include` with a link to a Dagster provided CI/CD template:
-    <CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/gitlab_template.yaml" language="yaml" />
+    <CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/gitlab_template.yaml" language="yaml" />
 
     Follow the link and replace the contents of your `.gitlab-ci.yml` with the YAML document at the link address. Otherwise, continue to the next step.
 
 3. Update the `PYTHON_VERSION` environment variable with your desired Python version
 
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/gitlab_python_version.yaml" language="yaml" title="Updating the Python version in .gitlab-ci.yml" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/gitlab_python_version.yaml" language="yaml" title="Updating the Python version in .gitlab-ci.yml" />
 
 </TabItem>
 <TabItem value="CLI" label="CLI">
@@ -101,7 +101,7 @@ Setting a custom base image isn't supported for GitLab CI/CD workflows out of th
     <Tabs groupId="method">
     <TabItem value="GitHub" label="GitHub">
     In your `.github/workflows/deploy.yml` file, add the `SERVERLESS_BASE_IMAGE_TAG` environment variable and set it to the tag printed out in the previous step:
-    <CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/github_base_image.yaml" language="yaml" title="Setting a custom base image in deploy.yml" />
+    <CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/github_base_image.yaml" language="yaml" title="Setting a custom base image in deploy.yml" />
 
     </TabItem>
 
@@ -132,7 +132,7 @@ To add data files to your deployment, use the [Data Files Support](https://setup
 ```
 
 If you want to include the data folder, modify your `setup.py` to add the `package_data` line:
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/data_files_setup.py" language="Python" title="Loading data files in setup.py" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/data_files_setup.py" language="Python" title="Loading data files in setup.py" />
 
 ## Disable PEX deploys
 
@@ -141,18 +141,18 @@ You have the option to disable PEX-based deploys and deploy using a Docker image
 <Tabs groupId="method">
 <TabItem value="GitHub" label="GitHub">
 In your `.github/workflows/deploy.yml` file, update the `ENABLE_FAST_DEPLOYS` environment variable to `false`:
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/github_disable_pex.yaml" language="yaml" title="Disable PEX deploys in deploy.yml" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/github_disable_pex.yaml" language="yaml" title="Disable PEX deploys in deploy.yml" />
 
 </TabItem>
 <TabItem value="GitLab" label="GitLab">
 1. Open your `.gitlab-ci.yml` file. If your `.gitlab-ci.yml` contains an `include` with a link to a Dagster provided CI/CD template:
-    <CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/gitlab_template.yaml" language="yaml" />
+    <CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/gitlab_template.yaml" language="yaml" />
 
     Follow the link and replace the contents of your `.gitlab-ci.yml` with the YAML document at the link address. Otherwise, continue to the next step.
 
 3. Update the `DISABLE_FAST_DEPLOYS` variable to `true`
 
-<CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/gitlab_disable_pex.yaml" language="yaml" title="Disable PEX deploys in .gitlab-ci.yml" />
+<CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/gitlab_disable_pex.yaml" language="yaml" title="Disable PEX deploys in .gitlab-ci.yml" />
 
 </TabItem>
 <TabItem value="CLI" label="CLI">
@@ -186,7 +186,7 @@ Setting a custom base image isn't supported for GitLab CI/CD workflows out of th
     <Tabs groupId="method">
     <TabItem value="GitHub" label="GitHub">
     In your `.github/workflows/deploy.yml` file, add the `SERVERLESS_BASE_IMAGE_TAG` environment variable and set it to the tag printed out in the previous step:
-    <CodeExample path="docs_beta_snippets/docs_beta_snippets/dagster-plus/deployment/serverless/runtime-environment/github_no_pex_custom_base_image.yaml" language="yaml" title="Setting a custom base image in `deploy.yml`" />
+    <CodeExample path="docs_snippets/docs_snippets/dagster-plus/deployment/serverless/runtime-environment/github_no_pex_custom_base_image.yaml" language="yaml" title="Setting a custom base image in `deploy.yml`" />
 
     </TabItem>
     <TabItem value="CLI" label="CLI">