From fe13e093093949abd446d4cf14dd94eae18e6a29 Mon Sep 17 00:00:00 2001 From: JamieDeMaria Date: Wed, 28 Aug 2024 14:27:52 -0400 Subject: [PATCH] pr comment --- docs/docs-beta/docs/guides/external-systems/apis.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs-beta/docs/guides/external-systems/apis.md b/docs/docs-beta/docs/guides/external-systems/apis.md index 790996e64600a..a973d32f98954 100644 --- a/docs/docs-beta/docs/guides/external-systems/apis.md +++ b/docs/docs-beta/docs/guides/external-systems/apis.md @@ -37,7 +37,7 @@ This example fetches the sunrise time for a given location from a REST API. Begi ## Step 2: Use the resource in an asset -To use the resource written in Step 1, you can provide it as a parameter to an asset: +To use the resource written in Step 1, you can provide it as a parameter to an asset after including it in the Definitions object: @@ -55,7 +55,7 @@ When you materialize `sfo_sunrise`, Dagster will provide a `SunResource` initial ## Step 4: Source configuration values from environment variables -Resources can also be configured with environment variables. You can use Dagster's built-in `EnvVar` class to source configuration values from environment variables at materialization time. +Resources can also be configured with environment variables. You can use Dagster's built-in `EnvVar` class to source configuration values from environment variables at materialization time. In this example, there is a new `home_sunrise` asset. Rather than hardcoding the location of your home, you can set it in environment variables, and configure the `SunResource` by reading those values: