s3 key.storage_class always 'STANDARD'

[lajarre]

Using boto 2.36.0

Having the key name corresponding to a Glacier-archived file (which was standard before), the following:

import boto.s3
conn = boto.s3.connect_to_region('eu-west-1', ...)
bu = conn.get_bucket('...')
k = bu.get_key(...)

print(k.storage_class)  # Gives 'STANDARD'

[jonathanwcrane]

That's funny, there's also a bug that a restored object remains as storage_class of "GLACIER" even though it's copyable and downloadable.

[jonathanwcrane]

BTW this is a duplicate of #2280 and/or #1173

[jacksonofalltrades]

This is extremely bad since our business logic depends heavily on storage_class being accurate. Is there an ETA on fixing this?

[jacksonofalltrades]

@jonathanwcrane That's not a bug, restored objects are always managed by glacier once they are in glacier. There is a separate property you can examine for restored objects called "ongoing_restore" to determine if it's being restored, was restored, or has not yet been restored.