By the way, what would be the best way to access and load the upstream partitions? Would it have to be a dynamic graph?

What is the best way to access the actual partitions list in this case? I can access

context.asset_partition_key_range

(for example,

PartitionKeyRange(start='2022-06-26', end='2022-07-06')

), but it only has the start and end of the partitions. As I understand, this is because

PartitionMapping

works this way. this is a little inconvenient, because different assets may have different partition schemas (daily, weekly, etc) and there is no clear way to get the exact partitions just from the

PartitionKeyRange

. Would you recommend a way of reconstructing the actual exact partitions list? I've managed to implement the IO Manager with hardcoded partition_key_range -> partitions_list mapping, but it's not a good general solution

Also, I get this error when trying to access

context.asset_partition_key

or

context.get_asset_identifier()

inside an IO Manager:

<http://context.log.info|context.log.info>(f"context.asset_partition_key_range: {context.asset_partition_key_range}")
<http://context.log.info|context.log.info>(f"context.has_partition_key: {context.has_partition_key}")
<http://context.log.info|context.log.info>(f"context.partition_key: {context.partition_key}")
<http://context.log.info|context.log.info>(f"context.asset_partition_key: {context.asset_partition_key}")

is this the desired behavior?

here is my code... I would be happy to get some tips for improvement