Two pieces of feedback around using per-asset metadata to control the behavior of the io manager configured for that asset: 1. It would be nice to have a special class of metadata that is NOT passed to the IO manager and is only used for display/data dictionary purposes. Letting business-centric metadata live in the same place as operational metadata can be dangerous if a user configures an asset with a metadata key that unknowingly matches with a key that the IO manager expects. 2. It would also be nice to have deploy-time validation of the per-asset metadata that an io manager expects, similar to the validation that can be done for resources. That way, if a user forgets to configure a necessary piece of metadata for the IO manager and no default is set, we can error earlier and avoid a runtime error

Hey @Leo Qin this is something i had been thinking about a while ago re IO manager specific metadata, but eventually deprioritized in favor of other improvements. I think surfacing this to a Github feature request would be helpful for us to gather more community feedback and prioritize the feature in out backlog. You can make a feature request here!

Done and done!