add refdoc links for swift

Author: Jamie Hannaford

doc/services/object-store/v1/account.rst

@@ -7,11 +7,13 @@ Show account details
 To work with an Object Store account, you must first retrieve an account object like so:
 
 .. sample:: object_store/v1/account/get.php
+.. refdoc:: OpenStack/ObjectStore/v1/Service.html#method_getAccount
 
 Get account metadata
 --------------------
 
 .. sample:: object_store/v1/account/get_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Account.html#method_getMetadata
 
 Replace all metadata with new values
 ------------------------------------
@@ -42,6 +44,7 @@ the metadata of the account will now be:
 To merge metadata, you must run:
 
 .. sample:: object_store/v1/account/reset_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Account.html#method_resetMetadata
 
 Merge new metadata values with existing
 ---------------------------------------
@@ -72,4 +75,5 @@ the metadata of the account will now be:
 
 To reset metadata, you must run:
 
-.. sample:: object_store/v1/account/merge_metadata.php
+.. sample:: object_store/v1/account/merge_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Account.html#method_mergeMetadata

doc/services/object-store/v1/containers.rst

@@ -5,6 +5,7 @@ Show details for a container
 ----------------------------
 
 .. sample:: object_store/v1/containers/get.php
+.. refdoc:: OpenStack/ObjectStore/v1/Service.html#method_getContainer
 
 At this point, the object returned is *empty* because we did not execute a HTTP request to receive the state of the
 container from the API. This is in accordance with one of the SDK's general policies of not assuming too much at the
@@ -25,6 +26,7 @@ List containers
 ---------------
 
 .. sample:: object_store/v1/containers/list.php
+.. refdoc:: OpenStack/ObjectStore/v1/Service.html#method_listContainers
 
 When listing containers, you must be aware that not *all* information about a container is returned in a collection.
 Very often only the object count, bytes used and container name will be exposed. If you would like to
@@ -39,10 +41,13 @@ access all of the remote state of a collection item, you can call ``retrieve`` l
 If you have a large collection of containers, this will slow things down because you're issuing a HEAD request per
 container.
 
+.. include:: /common/generators.rst
+
 Delete container
 ----------------
 
 .. sample:: object_store/v1/containers/delete.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Container.html#method_delete
 
 The API will only accept DELETE requests on containers when they are empty. If you have a container with any objects
 inside, the operation will fail.
@@ -51,6 +56,7 @@ Get metadata
 ------------
 
 .. sample:: object_store/v1/containers/get_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Container.html#method_getMetadata
 
 The returned value will be a standard associative array, or hash, containing arbitrary key/value pairs. These will
 correspond to the values set either when the container was created, or when a previous ``mergeMetadata`` or
@@ -60,6 +66,7 @@ Replace all metadata with new values
 ------------------------------------
 
 .. sample:: object_store/v1/containers/reset_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Container.html#method_resetMetadata
 
 In order to replace all existing metadata with a set of new values, you can use this operation. Any existing metadata
 items which not specified in the new set will be removed. For example, say an account has the following metadata
@@ -89,6 +96,7 @@ Merge new metadata values with existing
 ---------------------------------------
 
 .. sample:: object_store/v1/containers/merge_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Container.html#method_mergeMetadata
 
 In order to merge a set of new metadata values with the existing metadata set, you can use this operation. Any existing
 metadata items which are not specified in the new set will be preserved. For example, say an account has the following

doc/services/object-store/v1/objects.rst

@@ -5,6 +5,7 @@ Show details for an object
 --------------------------
 
 .. sample:: object_store/v1/objects/get.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Container.html#method_getObject
 
 At this point, the object returned is *empty* because we did not execute a HTTP request to receive the state of the
 container from the API. This is in accordance with one of the SDK's general policies of not assuming too much at the
@@ -26,6 +27,7 @@ Download an object
 ------------------
 
 .. sample:: object_store/v1/objects/download.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Object.html#method_download
 
 As you will notice, a Stream_ object is returned by this call. For more information about dealing with streams, please
 consult `Guzzle's docs`_.
@@ -37,6 +39,7 @@ List objects
 ------------
 
 .. sample:: object_store/v1/objects/list.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Container.html#method_listObjects
 
 When listing objects, you must be aware that not *all* information about a container is returned in a collection.
 Very often only the MD5 hash, last modified date, bytes used, content type and object name will be
@@ -51,12 +54,15 @@ returned. If you would like to access all of the remote state of a collection it
 
 If you have a large collection of $object, this will slow things down because you're issuing a HEAD request per object.
 
+.. include:: /common/generators.rst
+
 Create an object
 ----------------
 
 When creating an object, you can upload its content according to a string representation:
 
 .. sample:: object_store/v1/objects/create.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Container.html#method_createObject
 
 If that is not optimal or convenient, you can use a stream instead. Any instance of ``\Psr\Http\Message\StreamInterface``
 is acceptable. For example, to use a normal Guzzle stream:
@@ -76,21 +82,25 @@ uploading, this is what happens under the hood:
 To upload a DLO, you need to call:
 
 .. sample:: object_store/v1/objects/create_large_object.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Container.html#method_createLargeObject
 
 Copy object
 -----------
 
 .. sample:: object_store/v1/objects/copy.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Object.html#method_copy
 
 Delete object
 -------------
 
 .. sample:: object_store/v1/objects/delete.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Object.html#method_delete
 
 Get metadata
 ------------
 
 .. sample:: object_store/v1/objects/get_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Object.html#method_getMetadata
 
 The returned value will be a standard associative array, or hash, containing arbitrary key/value pairs. These will
 correspond to the values set either when the object was created, or when a previous ``mergeMetadata`` or
@@ -100,6 +110,7 @@ Replace all metadata with new values
 ------------------------------------
 
 .. sample:: object_store/v1/objects/reset_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Object.html#method_resetMetadata
 
 In order to replace all existing metadata with a set of new values, you can use this operation. Any existing metadata
 items which not specified in the new set will be removed. For example, say an account has the following metadata
@@ -129,6 +140,7 @@ Merge new metadata values with existing
 ---------------------------------------
 
 .. sample:: object_store/v1/objects/merge_metadata.php
+.. refdoc:: OpenStack/ObjectStore/v1/Models/Object.html#method_mergeMetadata
 
 In order to merge a set of new metadata values with the existing metadata set, you can use this operation. Any existing
 metadata items which are not specified in the new set will be preserved. For example, say an account has the following