Closed vsoch closed 5 years ago
Currently, when we add the "sizemb" key to the container metadata, it comes back as "Sizemb" because the casing isn't being honored by boto3. See the following issues / PRs for more details:
Since we can't enforce the fix upstream, in the meantime we will have to check for both.
Currently, when we add the "sizemb" key to the container metadata, it comes back as "Sizemb" because the casing isn't being honored by boto3. See the following issues / PRs for more details:
Since we can't enforce the fix upstream, in the meantime we will have to check for both.