Help needed with tags keyword of define_asset_job

[dagsir[bot]]

Hey team, I'm attempting to use the tags keyword of the define_asset_job function to customise the ECS launched runs CPU and Memory of a specific job, however it is still taking the default values applied in the dagster.yaml. Has anyone encountered this before and know how to solve it? This is my asset job definition:

generic_asset_job = define_asset_job(
    "generic_asset_job",
    selection=AssetSelection.groups("generic_group"),
    tags={
        "ecs/cpu": "16384",
        "ecs/memory": "32768",
    },
)

and this is my dagster.yaml:

scheduler:
  module: dagster.core.scheduler
  class: DagsterDaemonScheduler

run_coordinator:
  module: dagster.core.run_coordinator
  class: QueuedRunCoordinator

run_launcher:
  module: dagster_aws.ecs
  class: EcsRunLauncher
  config:
    include_sidecars: true
    secrets_tag: "dagster"
    run_resources:
      cpu: "8192"
      memory: "16384" # In MiB
      ephemeral_storage: 30 # In GiB (defaults to 20)

---

The question was originally asked in Dagster Slack.

[jamiedemaria]

This sounds like a bug, i'm going to create an issue for it

[jamiedemaria]

#17818

[garethbrickman]

Can't reproduce. Currently the tags parameter would only work to override the ECS run_resources if it was set in a pre-defined job, not if assets were selected and materialized in an ad hoc way in the UI. This example in the docs shows an op job, but it would work in an asset job too.