Only being able to specify the diag_table as a path (either local or GCS url) makes it challenging to get the diag_table into a kubernetes pod. This PR allows the user to use an asset dict (including a "bytes" asset dict) for the diag_table object. This means a literal representation of the diag_table can exist within the fv3config object, which will ease running the model with various diag tables on the cloud.
This implementation raises a ConfigError if the user specifies the wrong target name/location for the diag_table. Another perhaps more user-friendly option would just be to overwrite whatever the user provides for these parameters with the correct name/location.
Only being able to specify the
diag_tableas a path (either local or GCS url) makes it challenging to get thediag_tableinto a kubernetes pod. This PR allows the user to use an asset dict (including a "bytes" asset dict) for thediag_tableobject. This means a literal representation of thediag_tablecan exist within thefv3configobject, which will ease running the model with various diag tables on the cloud.This implementation raises a ConfigError if the user specifies the wrong target name/location for the diag_table. Another perhaps more user-friendly option would just be to overwrite whatever the user provides for these parameters with the correct name/location.