René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`storage.bucket.Bucket`:  add direct support for additional resource fields","articleBody":"The [Bucket API resource representation](https://cloud.google.com/storage/docs/json_api/v1/buckets) defines a number of fields as \"writable\", but which we don't already map:\n- `cors[]`\n- `lifecycle{}`\n- `location`\n- `logging{}`\n- `versioning{}`\n\nThe support for the `website{}` field is slightly odd (`Bucket.configure_website` / `Bucket.disable_website`), and should likely be normalized with support for the other fields.\n\n`Bucket.from_dict` currently captures them all in the key's metadata attribute, but that name creates confusion with its metadata key (which stores application-defined key-value pairs).\n\nI think it would be cleaner to map each the non-user-defined fields onto separate attributes, and propagate them to the server via the [insert](https://cloud.google.com/storage/docs/json_api/v1/buckets/insert), and [patch](https://cloud.google.com/storage/docs/json_api/v1/buckets/patch) or [update](https://cloud.google.com/storage/docs/json_api/v1/buckets/update) endpoints.\n\n`Bucket` should also expose read-only properties for the non-writable resource fields not already mapped, and which aren't constants:\n- `etag`\n- `id`\n- `metageneration`\n- `name`\n- `owner{}`\n- `projectNumber`\n- `selfLink`\n- `storageClass`\n- `timeCreated`\n","author":{"url":"https://github.com/tseaver","@type":"Person","name":"tseaver"},"datePublished":"2014-10-29T16:36:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/314/google-cloud-python/issues/314"}