Current implementation goes through the list of files to upload and finds the first file with realization id to get a template for the Realization and Iteration objects.
In theory, none of the files could be part of a realization. E.g. all of the files are aggregations. If this is the case, then no Realization and Iteration objects should be uploaded.
It is possible to determine, based on environment variables, whether we are running in a "realization" setting under ERT.
We should do a check on these variables instead of checking the file metadata one by one.
NOTE: This change will limit users so that Realization and Iteration objects only will be uploaded when running via ERT.
https://github.com/equinor/fmu-sumo-uploader/pull/83 introduces upload of realization and iteration objects.
Current implementation goes through the list of files to upload and finds the first file with realization id to get a template for the Realization and Iteration objects. In theory, none of the files could be part of a realization. E.g. all of the files are aggregations. If this is the case, then no Realization and Iteration objects should be uploaded.
It is possible to determine, based on environment variables, whether we are running in a "realization" setting under ERT. We should do a check on these variables instead of checking the file metadata one by one.
NOTE: This change will limit users so that Realization and Iteration objects only will be uploaded when running via ERT.