Bucket
Stores a new object and metadata.
Constructors
Properties
Access controls on the object.
Cache-Control directive for the object data. If omitted, and the object is accessible to all anonymous users, the default will be public, max-age=3600.
Number of underlying components that make up this object. Components are accumulated by compose operations.
Content-Disposition of the object data.
Content-Encoding of the object data.
Content-Language of the object data.
Content-Type of the object data. If an object is stored without a Content-Type, it is served as application/octet-stream.
Metadata of customer-supplied encryption key, if the object is encrypted by such a key.
A timestamp in RFC 3339 format specified by the user for an object.
Whether an object is under event-based hold. Event-based hold is a way to retain objects until an event occurs, which is signified by the hold's release (i.e. this value is set to false). After being released (set to false), such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is the loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false.
The content generation of this object. Used for object versioning.
Makes the operation conditional on whether the object's current generation matches the given value. Setting to 0 makes the operation succeed only if there are no live versions of the object.
Makes the operation conditional on whether the object's current generation does not match the given value. If no live object exists, the precondition fails. Setting to 0 makes the operation succeed only if there is a live version of the object.
Makes the operation conditional on whether the object's current metageneration matches the given value.
Makes the operation conditional on whether the object's current metageneration does not match the given value.
Not currently supported. Specifying the parameter causes the request to fail with status code 400 - Bad Request.
The version of the metadata for this object at this generation. Used for preconditions and for detecting changes in metadata. A metageneration number is only meaningful in the context of a particular generation of a particular object.
The owner of the object. This will always be the uploader of the object.
Apply a predefined set of access controls to this object.
Set of properties to return. Defaults to noAcl, unless the object resource specifies the acl property, when it defaults to full.
A server-determined value that specifies the earliest time that the object's retention period expires. This value is in RFC 3339 format. Note 1: This field is not provided for objects with an active event-based hold, since retention expiration is unknown until the hold is removed. Note 2: This value can be provided even when temporary hold is set (so that the user can reason about policy without having to first unset the temporary hold).
Storage class of the object.
Whether an object is under temporary hold. While this flag is set to true, the object is protected against deletion and overwrites. A common use case of this flag is regulatory investigations where objects need to be retained while the investigation is ongoing. Note that unlike event-based hold, temporary hold does not impact retention expiration time of an object.
The creation time of the object in RFC 3339 format.
The deletion time of the object in RFC 3339 format. Will be returned if and only if this version of the object has been deleted.
The time at which the object's storage class was last changed. When the object is initially created, it will be set to timeCreated.
The modification time of the object metadata in RFC 3339 format. Set initially to object creation time and then updated whenever any metadata of the object changes. This includes changes made by a requester, such as modifying custom metadata, as well as changes made by Cloud Storage on behalf of a requester, such as changing the storage class based on an Object Lifecycle Configuration.
The project to be billed for this request. Required for Requester Pays buckets.