osc object-store object show
Shows object metadata
Usage: osc object-store object show [OPTIONS] <CONTAINER> <OBJECT>
Arguments:
<CONTAINER>— The unique name for the account. An account is also known as the project or tenant<OBJECT>— The unique name for the object
Options:
--multipart-manifest <MULTIPART_MANIFEST>— If you include the multipart-manifest=get query parameter and the object is a large object, the object contents are not returned. Instead, the manifest is returned in the X-Object-Manifest response header for dynamic large objects or in the response body for static large objects--temp-url-sig <TEMP_URL_SIG>— Used with temporary URLs to sign the request with an HMAC-SHA1 cryptographic signature that defines the allowed HTTP method, expiration date, full path to the object, and the secret key for the temporary URL. For more information about temporary URLs, see Temporary URL middleware--temp-url-expires <TEMP_URL_EXPIRES>— The date and time in UNIX Epoch time stamp format or ISO 8601 UTC timestamp when the signature for temporary URLs expires. For example, 1440619048 or 2015-08-26T19:57:28Z is equivalent to Mon, Wed, 26 Aug 2015 19:57:28 GMT. For more information about temporary URLs, see Temporary URL middleware--filename <FILENAME>— Overrides the default file name. Object Storage generates a default file name for GET temporary URLs that is based on the object name. Object Storage returns this value in the Content-Disposition response header. Browsers can interpret this file name value as a file attachment to save. For more information about temporary URLs, see Temporary URL middleware--symlink <SYMLINK>— If you include the symlink=get query parameter and the object is a symlink, then the response will include data and metadata from the symlink itself rather than from the target