Any reason why the dbt

target

isn’t accepted by

load_assets_from_dbt_project

? I’m currently facing an issue with that since I need to extract some information from the manifest that changes depending on the target (different dbs for dev and prod, need them to be part of the asset keys). Happy to open a PR if there’s no reason it’s not currently supported.

chatted a bit about this offline, and in most cases I think you should prefer not to have your asset keys change between environments, as this makes it difficult for downstream assets from your dbt assets to retain a constant definition (so in essence, it can commit you to need to have all asset keys across your platform modify their upstream deps between envs). Instead, solutions which vary IOManager behavior between environments should be preferred when possible.

To close this off in case anyone comes across this, I wound up using a

ResourceDefinition.hardcoded_resource()

inside my IO Manager, this is enough for my fairly simple use case, otherwise I could have scoped the

dbt_cli_resource

into my IO manager and done a little more parsing