#13945·dagster

group_name on `OutputContext` and `InputContext`

Author: drawnwrenCreated Apr 27, 2023Updated Sep 15, 2026
Labelstype: good first issuetype: feature-request

What's the use case?

We use group_name to logically group assets on the front-end but the io-manager can't see the groups. It would be nice to also be able to get group_name from the context in an io-manager (without having to manually add it to metadata in each asset) to maintain the logically groupings in the materializations as well.

Ideas of implementation

We probably want to call the property asset_group_name for maximum clarity.

Additional information

Best current workaround is to use the following, in either handle_output or load_input:

python
        group_name = context.step_context.job_def.asset_layer.assets_def_for_asset(
            context.asset_key
        ).group_names_by_key[context.asset_key]

Message from the maintainers

Impacted by this issue? Give it a ! We factor engagement into prioritization.