Skip to main content

Configuring assets using the Dagster UI

You will commonly want to manually materialize assets using the Dagster UI to backfill historical data, debug a production issue, or some other one-off task.

Often, you will want to be able to tweak some parameters when materializing these assets. This can be accomplished through the asset configuration system.

What you'll learn​

  • How to make your assets configurable
  • How to provide configuration when launching a run
Prerequisites

To follow the steps in this guide, you'll need:

Making assets configurable​

For an asset to be configurable, you must first define a schema that inherits from the Dagster Config class. For example, let's say we want to allow users to change the lookback time window for the computation that materializes an asset:

Adding configuration
Loading...

Providing configuration when launching a run​

When launching a run using Dagster's Launchpad, you can provide a run config file as YAML or JSON that overrides the default configuration for your asset:

Run config provided via UI
Loading...

Run configurations reference an op which is the underlying compute associated with an asset. See the Ops vs Assets documentation for more information.