You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/guides/labs/components/existing-code-location.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This feature is still in development and might change in patch releases. It’s
11
11
12
12
:::note
13
13
14
-
This guide is only relevant if you are starting from an _existing_ Dagster code location. This setup is unnecessary if you used `dg code-location generate` to create your code location.
14
+
This guide is only relevant if you are starting from an _existing_ Dagster code location. This setup is unnecessary if you used `dg scaffold code-location` to create your code location.
Copy file name to clipboardExpand all lines: docs/docs/guides/labs/components/index.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ First let's set up Sling. If we query the available component types in our envir
106
106
This is because the basic `dagster-components` package (which was installed when we scaffolded our code location) is lightweight and doesn't include components for specific integrations (like Sling). We can get access to a Sling component by installing the `sling` extra of `dagster-components`:
107
107
108
108
:::note
109
-
Recall that `dg` always operates in an isolated environment-- so how is it able to access the set of components types available in our project environment? Under the hood, `dg` attempts to resolve a project root whenever it is run. If it finds a `pyproject.toml` file with a `tool.dg.is_code_location = true` setting, then it will by default expect a `uv`-managed virtual environment to be present in the same directory (this can be confirmed by the presence of a `uv.lock` file). When you run commands like `dg component-type list`, `dg` obtains the results by identifying the in-scope project environment and querying it. In this case, the project environment was set up for us as part of the `dg code-location scaffold` command.
109
+
Recall that `dg` always operates in an isolated environment-- so how is it able to access the set of components types available in our project environment? Under the hood, `dg` attempts to resolve a project root whenever it is run. If it finds a `pyproject.toml` file with a `tool.dg.is_code_location = true` setting, then it will by default expect a `uv`-managed virtual environment to be present in the same directory (this can be confirmed by the presence of a `uv.lock` file). When you run commands like `dg list component-type`, `dg` obtains the results by identifying the in-scope project environment and querying it. In this case, the project environment was set up for us as part of the `dg scaffold code-location` command.
There it is: `dagster_components.dbt_project`. We can access detailed info about a component type using the `dg component-type info` command. Let's have a look at the `dagster_components.dbt_project` component type:
180
+
There it is: `dagster_components.dbt_project`. We can access detailed info about a component type using the `dg info component-type` command. Let's have a look at the `dagster_components.dbt_project` component type:
You might notice the typo in the above file - after updating a component file, it's often useful to validate that the changes match the component's schema. You can do this by running `dg component check`:
205
+
You might notice the typo in the above file - after updating a component file, it's often useful to validate that the changes match the component's schema. You can do this by running `dg check component`:
Copy file name to clipboardExpand all lines: docs/docs/guides/labs/components/using-a-component.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,13 @@ This feature is still in development and might change in patch releases. It’s
15
15
You can view the available component types in your environment by running the following command:
16
16
17
17
```bash
18
-
dg component-type list
18
+
dg list component-type
19
19
```
20
20
21
21
This will display a list of all the component types that are available in your project. If you'd like to see more information about a specific component, you can run:
22
22
23
23
```bash
24
-
dg component-type docs<component-name>
24
+
dg docs component-type <component-name>
25
25
```
26
26
27
27
This will display a webpage containing documentation for the specified component type.
@@ -31,7 +31,7 @@ This will display a webpage containing documentation for the specified component
31
31
Once you've selected the component type that you'd like to use, you can instantiate a new component by running:
This will create a new directory underneath your `components/` folder that contains a `component.yaml` file. Some components may also generate additional files as needed.
@@ -46,7 +46,7 @@ The `component.yaml` is the primary configuration file for a component. It conta
46
46
To see a sample `component.yaml` file for your specific component, you can run:
Copy file name to clipboardExpand all lines: examples/docs_beta_snippets/docs_beta_snippets/guides/components/existing-project/8-dg-list-component-types.txt
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
dg component-type list
1
+
dg list component-type
2
2
3
3
Using /.../my-existing-project/.venv/bin/dagster-components
Copy file name to clipboardExpand all lines: examples/docs_beta_snippets/docs_beta_snippets/guides/components/index/23-dg-component-check-error.txt
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
dg component check
1
+
dg check component
2
2
3
3
/.../jaffle-platform/jaffle_platform/components/jdbt/component.yaml:8 - Unable to parse YAML: while scanning a quoted scalar, found unexpected end of stream
Copy file name to clipboardExpand all lines: examples/docs_beta_snippets/docs_beta_snippets/guides/components/shell-script-component/3-dg-list-component-types.txt
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
dg component-type list
1
+
dg list component-type
2
2
3
3
Using /.../my-component-library/.venv/bin/dagster-components
Copy file name to clipboardExpand all lines: examples/docs_beta_snippets/docs_beta_snippets/guides/components/shell-script-component/6-scaffold-instance-of-component.txt
Copy file name to clipboardExpand all lines: examples/docs_beta_snippets/docs_beta_snippets_tests/snippet_checks/guides/components/test_component_docs_existing_code_location/test_existing_code_location.py
Copy file name to clipboardExpand all lines: examples/docs_beta_snippets/docs_beta_snippets_tests/snippet_checks/guides/components/test_components_docs.py
0 commit comments