What is a good way to get correct asset keys for AssetIn?

[danielgafni]

I have a bunch of assets defined in different Python modules.

I am adding key prefixes to these assets with dg.load_assets_from_current_module.

How do I specify cross-module dependencies on different assets without hard-coding the final asset key into dg.AssetIn? This approach seems fragile because the assets key are likely to change in the future, which means all the dg.AssetIn referencing these keys will have to be manually updated too.

If load_assets_from_current_module modified asset defs in-place, then it would be possible to import the original AssetsDefinition object and pass it's .key attribute to AssetIn. But there are probably good reasons load_assets_from_current_module it's doing this.

[danielgafni]

@cmpadden Feeling lonely here, is there any official guidance available?

Relevant components comment: #28472 (comment)

[cmpadden]

Hey @danielgafni - will try to get an answer for you. In the meantime could you please provide a minimum example?

[cmpadden]

@danielgafni, after chatting a bit with another engineer, I'm not sure if there is an ideal workaround to this right now other than the hard-coding that you're currently doing. It seems to be a known limitation of the load_assets_from_current_module function at this point in time.

[danielgafni]

Oh, ok. That's unfortunate.