The current implementation saves only the most recent timestamp whenever status information in status_history is updated, and all previous information is deleted.

Let’s change the data structure to a List to ensure that previous information is not lost.

Details

• For compatibility with the existing API, the status_history field in compute_session GQL will remain unchanged. Instead, let’s deprecate status_history and add a new field called status_history_log.

  Discussion

@fregataa I have a few questions regarding the task.

• Should we retain the status_history legacy field in the new API (compute_session_node) as well? Personally, I think it might be better to remove the deprecated status_history and keep only status_history_log.

• Unlike compute_session, the compute_container GQL does not have a status_history field. Is there a specific reason why compute_container does not have a status_history field? If not, I think it would be better to add status_history_log.