Add "dagster/io_manager_key" metadata to assets

[HynekBlaha]

Hello,
Would it be possible to fill metadata dagster/io_manager_key to all assets (if available)?
This metadata value is already being set for AssetSpec, but not for @asset.

Why?
I would like to generate DataHub definitions from Dagster GraphQL.
There is no way to identify which IO Manager is used for asset.
Without this information, I am unable to identify where the input/output data is stored (e.g. database.namespace.table / storage_account.container.blob / API).

Could there be any unexpected downside?

My query:

query {
  # For each active repository
  repositoriesOrError {
    ... on RepositoryConnection {
      nodes {
        allTopLevelResourceDetails {
          id
          name
          resourceType
          configuredValues { key, value, type }
          configFields {
            name
            description
            configType { description }
          	configTypeKey
            defaultValueAsJson
          }
          assetKeysUsing {path}
          nestedResources {name, resource {id}}
        }
        # Get repository name
        location { name }
        # Get jobs with metadata list
        jobs {
          # Get job name
          name
          # Get job metadata
          metadataEntries {
            label
            # If value is type TextMetadataEntry, show text field
            ... on TextMetadataEntry {
              text
            }
          }
        }
        # Get assets with metadata list
        assetNodes {
          # Get asset key
          assetKey { path }
          op {outputDefinitions {name, metadataEntries {
            description
          }}}
          configField {name}
          requiredResources { resourceKey }
          owners {
            ... on UserAssetOwner {
              email
            }
            ... on TeamAssetOwner {
              team
            }
          }
          # Get asset metadata
          metadataEntries {
            label
            # If value is type TextMetadataEntry, show text field
            ... on TextMetadataEntry {
              text
            }
            ... on AssetMetadataEntry {
              label
            }
          }
          tags {
            key
            value
          }
        }
      }
    }
  }
}

[cmpadden]

Hi @HynekBlaha - we discussed this feature internally today, and agreed that it's something that we should look into implementing, however, we'll need to more thoroughly review what is available to us on the assets given the i/o manager implementation and possible edge case considerations. Will keep you posted with any updates.

Thanks.