When outputs are tied to assets, include OutputDefinition metadata in AssetMaterialization

[sryza]

Use Case

Users are currently responsible for passing through output metadata to their asset materializations. It would be convenient if the yield EventMetadataEntry below was not required.

class MyIOManager(IOManager):
    def handle_output(self, context, value):
        ...
        yield EventMetadataEntry.text(context.metadata["path"], label="path")

    def get_output_asset_key(self, context):
        ...

@solid(output_defs=OutputDefinition(metadata={"path": "/a/b/c"}))
def my_solid():
    ...

Ideas of Implementation

This would require some sort of schematization of output metadata so that it's displayable in Dagit.

Additional Info

---

Message from the maintainers:

Excited about this feature? Give it a 👍. We factor engagement into prioritization.

[sryza]

With SDAs and associated metadata, we no longer need this