docs: clarified where ordering_key will be written if write_metadata …

…is set (#965)

* docs: clarified where ordering_key will be written if write_metadata is set

PiperOrigin-RevId: 551210991

Source-Link: googleapis/googleapis@7c762d7

Source-Link: googleapis/googleapis-gen@15fe4c5
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiMTVmZTRjNWZmNWViZDUyOTExYjQyOWIwNWI5OTJlMjMyZjUzMzUxZSJ9

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

google/pubsub_v1/types/pubsub.py

@@ -1277,7 +1277,11 @@ class AvroConfig(proto.Message):
             write_metadata (bool):
                 When true, write the subscription name, message_id,
                 publish_time, attributes, and ordering_key as additional
-                fields in the output.
+                fields in the output. The subscription name, message_id, and
+                publish_time fields are put in their own fields while all
+                other message properties other than data (for example, an
+                ordering_key, if present) are added as entries in the
+                attributes map.
         """
 
         write_metadata: bool = proto.Field(

samples/generated_samples/snippet_metadata_google.pubsub.v1.json

@@ -8,7 +8,7 @@
     ],
     "language": "PYTHON",
     "name": "google-cloud-pubsub",
-    "version": "2.18.0"
+    "version": "0.1.0"
   },
   "snippets": [
     {