Change Details

Rather than add a legacy flag onto the existing ComputeLogManager (D7945), this diff creates a separate interface for a InstanceLogManager class. We could either do inheritance checks on the instance compute log manager, or pull this out as as a separate property on the instance. The new API explicitly separates out the log file data and the log file metadata. It also adds an abstractmethod `log_event`, which can either initialize an in-process DagsterLogManager and call log (outside of a pipeline context), or initialize the python logging handlers (@sandyryza, RFC). This should be called from `DagsterInstance.handle_new_event` (e.g. whenever we are creating an event outside of a pipeline context)

Rather than add a legacy flag onto the existing ComputeLogManager (D7945), this diff creates a separate interface for a CapturedLogManager class. The plan is to do inheritance checks on the instance compute log manager and then begin issuing warnings on instance init if the compute log manager does not implement the newer interface. The new API explicitly separates out the log file data and the log file metadata.

Rather than add a legacy flag onto the existing ComputeLogManager (D7945), this diff creates a separate interface for a InstanceCapturedLogManager class. We couldThe plan is to either do inheritance checks on the instance compute log manager, or pull this out as and then begin issuing as a separate property onwarnings on instance init if the compute log manager does not implement the instancenewer interface. The new API explicitly separates out the log file data and the log file metadata. It also adds an abstractmethod `log_event`, which can either initialize an in-process DagsterLogManager and call log (outside of a pipeline context), or initialize the python logging handlers (@sandyryza, RFC). This should be called from `DagsterInstance.handle_new_event` (e.g. whenever we are creating an event outside of a pipeline context)