AssetExecutionContext API simplification

[jamiedemaria]

We are undertaking an effort to simplify the API of the AssetExecutionContext. This will involve deprecating some methods on AssetExecutionContext, but will result in a context that is easier to navigate and more intuitive to use. All methods that are deprecated on AssetExecutionContext will have alternatives. This is an ongoing effort and this discussion will be updated as methods are marked deprecated.

deprecated	replacement
context.op_config	context.op_execution_context.op_config
context.node_handle	context.op_execution_context.node_handle
context.op_handle	context.op_execution_context.op_handle
context.op	context.op_execution_context.op
context.get_mapping	context.op_execution_context.get_mapping
context.selected_output_names	context.op_execution_context.selected_output_names
asset_partition_key_for_output	context.partition_key
context.asset_partition_keys_for_output	context.partition_keys
context.asset_partitions_time_window_for_output	context.partition_time_window
context.asset_partition_key_range_for_output	context.partition_key_range
context.dagster_run	context.run
context.run_id	context.run.run_id
context.run_config	context.run.run_config
context.run_tags	context.run.tags
context.has_tag	key in context.run.tags
context.get_tag	context.run.tags.get(key)
context.get_op_execution_context	context.op_execution_context

Note that even though they are marked deprecated, these methods will not be removed from AssetExecutionContext until a future version of Dagster. You can continue to access these methods, but will receive deprecation warnings.

If you want to continue to use the deprecated methods without getting deprecation warnings, you can modify the type annotation of the context passed to your assets to OpExecutionContext

@asset 
def my_asset(context: OpExecutionContext):
    context.op_config # no deprecation warning