This page discusses the metadata fields that are stored along with buckets in Cloud Storage.
Buckets created in Cloud Storage have metadata associated with them. Metadata identifies properties of the bucket and specifies how the bucket should be handled when it's accessed.
Some metadata exists as
key: value pairs. For example, the name of a bucket is
represented by the metadata entry
name: my-bucket-name for the JSON API. The
XML API presents such metadata as
<elements></elements>, such as
<LocationConstraint>US</LocationConstraint> for the bucket location.
Other metadata can have an array of data associated with the key. For example, the lifecycle management metadata can contain a set of rules that apply to current and future objects in a bucket.
The mutability of metadata varies:
Some you can only view.
Some you can only set when the bucket is first created, and cannot edit or remove.
Some you can add and edit, but not remove.
Some you can add, edit, and remove at any time.
The following metadata is set during bucket creation, and cannot be edited or removed:
The project the bucket is a part of
- A bucket's metageneration number uniquely identifies the metadata state of
the bucket. The metageneration number is
1at the time of bucket creation and increases each time you modify the bucket's metadata.
- A bucket's metageneration number uniquely identifies the metadata state of the bucket. The metageneration number is
Editable bucket metadata is metadata whose values you can typically modify at any time. In some cases, such as the bucket being subject to an organization policy constraint, there are restrictions on modifying certain metadata values.
1 This metadata cannot be viewed or managed using the XML API.
2 You can use the XML API to set this metadata during bucket creation, but not to view or manage this metadata.