Skip to content
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.

Sign up for GitHub

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] add example using EnvVar.get_value() method #23392

Merged
merged 2 commits into from
Aug 19, 2024
+8 −0
Merged

[docs] add example using EnvVar.get_value() method #23392

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c262af
[docs] add example using EnvVar.get_value() method
garethbrickman Aug 2, 2024
a0807ee
fix indent
garethbrickman Aug 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/content/guides/dagster/using-environment-variables-and-secrets.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,14 @@ deployment_name = os.getenv("DAGSTER_CLOUD_DEPLOYMENT_NAME")

Refer to the [Dagster+ Branch Deployments example](#example-2-dagster-branch-deployments) for a real-world example.

You can also call the `get_value()` method on the `EnvVar`:

```python
from dagster import EnvVar

database_name = EnvVar('DATABASE_NAME').get_value()
```

### From Dagster configuration

[Configurable Dagster objects](/concepts/configuration/config-schema) - such as ops, assets, resources, I/O managers, and so on - can accept configuration from environment variables. Dagster provides a native way to specify environment variables in your configuration. These environment variables are retrieved at launch time, rather than on initialization as with `os.getenv`. Refer to the [next section](#using-envvar-vs-osgetenv) for more info.
Expand Down