Hey dagster team - I'm trying the following code after upgrading to 0.15.0:

# Run config no longer works from passing it in. Must use launch pad
run_config_path = dagster.file_relative_path(
    __file__, os.path.join(".", "run_config", "vocational_assets_job.yaml")
)
config = dagster.config_from_files([run_config_path])
vocational_assets_job = dagster.build_assets_job(
    assets=[*extract_assets, *load_assets, *transform_assets],
    name="vocational_assets_job",
    config=config,
)

However, the config doesn't work and it still requires me to pass in via launchpad. Whats the best way to set a default config?

Hi Charles. In 0.15.0, we've switched to defining asset jobs via

define_asset_job

instead of

build_assets_job

in order to allow asset definitions to live directly on repositories. You can rewrite your job definition as follows:

vocational_assets_job = define_asset_job("vocational_assets_job", config=config).resolve(
    [my_asset], source_assets=[]
)

Ah thank you! i'll give that a shot

If you add your asset job to a repository, you can directly just write

vocational_assets_job = define_asset_job("vocational_assets_job", config=config)

and dagster will make the resolve call for you

😄 appreciate the fast turnaround

Oh I see, you're seeing this error from the materialize button. It seems there is a bug in passing predefined config on your job to display in Dagit in the launchpad modal. I'll file an issue, for now you you can execute from the launchpad (and this will prepopulate the config from your yaml correctly).

Thank you so much!

@Dagster Bot issue Config on asset job doesn't populate in materialize launchpad modal

Created issue at: https://github.com/dagster-io/dagster/issues/8469

@sean - mind taking a look?

looking into it