Summary & Motivation

Extracts compute log operations from DagsterInstance into a dedicated ComputeLogDomain following the established domain pattern used by other areas like RunDomain, DaemonDomain, etc. This addresses an API inconsistency where compute log operations required direct access to instance.compute_log_manager.* rather than having wrapper methods on DagsterInstance like other functional areas.

The refactor provides:

• Consistent API surface: New wrapper methods like instance.get_compute_log_data(), instance.capture_compute_logs(), etc.
• Enhanced functionality: Additional business logic including error handling, logging, and convenience methods
• Backward compatibility: All existing instance.compute_log_manager.* calls continue to work unchanged

Key new methods include:

# Core operations
instance.capture_compute_logs(log_key)
instance.get_compute_log_data(log_key, cursor, max_bytes)
instance.delete_compute_logs(log_key=log_key)

# Convenience methods
instance.get_compute_logs_for_run(run_id, step_key)
instance.cleanup_compute_logs_for_run(run_id)

How I Tested These Changes

New unit tests verify all wrapper methods delegate correctly to the underlying ComputeLogManager. All existing functionality remains unchanged.