aliyun-oss-sdk 0.0.3 → 0.1.0

data/wiki/cors.md

@@ -0,0 +1,59 @@
+## CORS
+
+CORS allow web application visit resources not belongs it's domain. OSS provide interface to help developer control the premissions.
+
+
+### Set CORS
+
+
+With Client#bucket_enable_cors, you can set cors easily:
+
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host = "oss-cn-hangzhou.aliyuncs.com"
+    bucket = "bucket-name"
+    client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
+    
+    rule = Aliyun::Oss::Struct::Cors.new(allowed_methods: ['get'], allowed_origins: ['*'])
+	res = client.bucket_enable_cors([rule])
+    puts res.success?, res.headers
+
+More about the rules, visit [OSS API](https://docs.aliyun.com/#/pub/oss/api-reference/cors&PutBucketcors) and [Struct::Cors]()
+
+
+### Get CORS Rules
+
+To get current cors rules, you can use Client#bucket_get_cors:
+
+    
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host = "oss-cn-hangzhou.aliyuncs.com"
+    bucket = "bucket-name"
+    client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
+    
+	res = client.bucket_get_cors
+    puts res.success?, res.parsed_response
+
+    
+### Disable CORS
+
+If you want to diable CORS, just like below:
+
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host = "oss-cn-hangzhou.aliyuncs.com"
+    bucket = "bucket-name"
+    client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
+    
+    # create a private bucket on oss-cn-beijing
+	res = client.bucket_disable_cors
+    puts res.success?, res.headers
+    
+Note: disable CORS will remove all existing CORS Rules.
+
+
+Now, Let's go to next section: [LifeCycle](./lifecycle.md)      

data/wiki/error.md

@@ -24,35 +24,46 @@ Here,
 
 # Error Code
 
-| code  |  summary |
+| code  |  summary |  HTTP Status|
 |---|---|
-|AccessDenied	|Access denied |
-|BucketAlreadyExists	| Bucket Already Exist|
-|BucketNotEmpty	|Bucket Not Empty|
-|EntityTooLarge	| Entry Too Large|
-|EntityTooSmall	| Entry Too Small|
-|FileGroupTooLarge	|File Group Too Large|
-|FilePartNotExist	|File Part Not Exist|
-|FilePartStale	| File Part Expired|
-|InvalidArgument	|Invalid Argument|
-|InvalidAccessKeyId | Access Key ID Not Exist|
-|InvalidBucketName	| The specified bucket is not valid.|
-|InvalidDigest	| Invalid Digest |
-|InvalidObjectName	|Invalid Object Name|
-|InvalidPart	| Invalid Part|
-|InvalidPartOrder	|Invalid Part Order|
-|InvalidTargetBucketForLogging	|Invalid Target Bucket For Logging|
-|InternalError	|Internal Error|
-|MalformedXML	|Malformed XML|
-|MethodNotAllowed	|Method Not Allowed|
-|MissingArgument	|Missing Argument|
-|MissingContentLength	|Missing Content Length|
-|NoSuchBucket	|No Such Bucket|
-|NoSuchKey	|No Such Key|
-|NoSuchUpload	|Multipart Upload ID Not Exist|
-|NotImplemented	|Not Implemented|
-|PreconditionFailed	|Precondition Failed|
-|RequestTimeTooSkewed	|Request Time Large Than 15 minutes|
-|RequestTimeout	|Request Timeout|
-|SignatureDoesNotMatch	|Signature Does Not Match|
-|TooManyBuckets	|Too Many Buckets|
+|AccessDenied	|Access denied | 403|
+|BucketAlreadyExists	| Bucket Already Exist|	409|
+|BucketNotEmpty	|Bucket Not Empty|	409|
+|EntityTooLarge	| Entry Too Large|	400|
+|EntityTooSmall	| Entry Too Small|	400|
+|FileGroupTooLarge	|File Group Too Large|	400|
+|InvalidLinkName	| Object Link Same With Object| 400|
+|LinkPartNotExist	| Object Not Exist| 400|
+|ObjectLinkTooLarge	| Object Too Much | 400|
+|FieldItemTooLong	| Field Too Large| 400|
+|FilePartInterity	| File Part Already Changed| 400|
+|FilePartNotExist	|File Part Not Exist|	400|
+|FilePartStale	| File Part Expired|	400|
+|IncorrectNumberOfFilesInPOSTRequest|	File Count Invalid| 400|
+|InvalidArgument	|Invalid Argument|	400|
+|InvalidAccessKeyId | Access Key ID Not Exist| 403|
+|InvalidBucketName	| The specified bucket is not valid.| 400|
+|InvalidDigest	| Invalid Digest | 400|
+|InvalidEncryptionAlgorithmError	| Specified Encoding-Type Error | 400|
+|InvalidObjectName	|Invalid Object Name| 400
+|InvalidPart	| Invalid Part| 400|
+|InvalidPartOrder	|Invalid Part Order| 400|
+|InvalidPolicyDocument	| Invalid Policy| 400|
+|InvalidTargetBucketForLogging	|Invalid Target Bucket For Logging| 400|
+|InternalError	|Internal Error| 500|
+|MalformedXML	|	XML Invalid| 400|
+|MalformedPOSTRequest | Requested XML Invalid | 400|
+|MaxPOSTPreDataLengthExceededError	| Body except file Too Large | 400|
+|MethodNotAllowed	|Method Not Allowed| 405|
+|MissingArgument	|Missing Argument| 411|
+|MissingContentLength	|Missing Content Length| 411|
+|NoSuchBucket	|No Such Bucket| 404|
+|NoSuchKey	|No Such Key| 404|
+|NoSuchUpload	|Multipart Upload ID Not Exist| 404|
+|NotImplemented	|Not Implemented| 501|
+|PreconditionFailed	|Precondition Failed| 412|
+|RequestTimeTooSkewed	|Request Time Large Than 15 minutes| 403|
+|RequestTimeout	|Request Timeout| 400|
+|RequestIsNotMultiPartContent | Content-Type Invalid| 400|
+|SignatureDoesNotMatch	|Signature Does Not Match|403|
+|TooManyBuckets	|Too Many Buckets| 400|

data/wiki/get_start.md

@@ -2,23 +2,24 @@
 
 Here, you can know how to do some basic operation with Aliyun OSS SDK.
 
+
 ### Step-1. Init a client
 
-Mostly API are handled by Aliyun::Oss::Client class, now Let's create a instance:
+Mostly OSS API are handled by [Aliyun::Oss::Client](http://www.rubydoc.info/gems/aliyun-oss-sdk/Aliyun/Oss/Client) class, Let's create a instance first:
 
     require 'aliyun/oss'
     
     access_key, secret_key = "your id", "your secret"
     host = "oss-cn-hangzhou.aliyuncs.com"
-    bucket = "oss-sdk-dev-test"
+    bucket = "bucket-name"
     client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
 
-Here, access_key/secret_key is is your access credentials, Aliyun provide three ways to fetch them, read detail at https://docs.aliyun.com/#/pub/oss/product-documentation/acl&RESTAuthentication, more about the [Aliyun::Oss::Client]()
+Here, access_key/secret_key is is your access credentials, Aliyun provide three ways to get access credentials, get more information [here](https://docs.aliyun.com/#/pub/oss/product-documentation/acl&RESTAuthentication).
 
 
 ### Step-2. Create Bucket
 
-Buckets are global in OSS, so keep your bucket name unique with others. It can used to store many objects. Now, we create a bucket:
+Buckets are global object in OSS, so find a uniqueness name for your bucket, Or it fail when create. It can used to store objects. Now, we create a bucket:
 
     require 'aliyun/oss'
     
@@ -30,33 +31,49 @@ Buckets are global in OSS, so keep your bucket name unique with others. It can u
     res = client.bucket_create('new-bucket', 'oss-cn-beijing', 'private')
     puts res.success?, res.headers
     
-Default, most api return a [HttpartyResponse](http://www.rubydoc.info/github/jnunemaker/httparty/HTTParty/Response), you can use much methods to fetch your interesting message.
+In our library, most instance methods of Client return [HttpartyResponse](http://www.rubydoc.info/github/jnunemaker/httparty/HTTParty/Response), you can use rich methods to fetch your interesting message.
+
 
 ### Step-3 Upload Object
 
-Object is the most basic unit of data in OSS, mostly it's a file. you can upload a object:
+Object is the most basic unit of data in OSS, you can simple imagine it's just a file. here, we upload a object to OSS:
 
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host, bucket = "oss-cn-hangzhou.aliyuncs.com", "bucket-name"
     client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
     
     file = File.new("path/to/test.txt")
     res = client.bucket_create_object("test.txt", file)
     puts res.success?, res.headers
 
+
 ### Step-4 list all object
 
 After you complete some upload, maybe you want to list the objects in the bucket:
 
+
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host, bucket = "oss-cn-hangzhou.aliyuncs.com", "bucket-name"
     client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
     
     res = client.bucket_list_objects()
     puts res.success?, res.parsed_response
 
-With correct parameters, you can get more flexible result.
+With correct parameters, you can get more flexible result. you can get detailed Paramters [here](http://www.rubydoc.info/gems/aliyun-oss-sdk/Aliyun%2FOss%2FClient%3Abucket_list_objects).
+
 
 ### Step-5. Get special object
 
 Now, you want to get a special object:
 
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host, bucket = "oss-cn-hangzhou.aliyuncs.com", "bucket-name"
     client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
     
     res = client.bucket_get_object("test.txt")

data/wiki/installation.md

@@ -2,7 +2,7 @@
 
 It's a Ruby Gem, so you can install it like any Gem:
 
-    gem install aliyun-oss-sdk
+    $ gem install aliyun-oss-sdk
 
 If you use Gemfile manage your Gems, Add below to your Gemfile.
 
@@ -10,6 +10,6 @@ If you use Gemfile manage your Gems, Add below to your Gemfile.
 
 And run:
 
-    bundle install
+    $ bundle install
     
 Now, [Getting started](./get_start.md)    

data/wiki/lifecycle.md

@@ -0,0 +1,75 @@
+## LifeCycle
+
+OSS provide LifeCycle to help user manage lifecycle of object. User can create LifeCycle rules to manage objects. At present, user can create rule to auto delete Objects. Each rule is composed by following several parts:
+
++ Prefix of Object name, only match the prefix will apply this rule.
++ Operation, user want to take for the matched objects.
++ Date or Days, which user can specify expired date or days to expire.
+
+
+### Set LifeCycle
+
+
+In the LifeCycle, you can contains 1000 rules at max.
+
+Each rule contains:
+
++ ID: each rule ID must keep uniqueness and cannot contain others(eg: abc and abcd).
++ Prefix: it can used to apply rule for object with the prefix
++ Status: defined the status for the rule, Only support Enabled and Disabled.
++ Expiration: Date or Days, used to specify expired date or specify expired after x days from last modified date.
+
+In our Library, to use Struct::LifeCycle to define a rule:
+
+     # Define a rule to auto delete objects with prefix: logs-prod- after 7 days since last modified date
+    rule1 = Aliyun::Oss::Struct::LifeCycle.new({ prefix: 'logs-prod-', days: 7, enable: true })
+	
+	# Defome a ri;e tp auto delete objects with prefix: logs-dev- at Time.now + 24*60*60
+	rule2 = Aliyun::Oss::Struct::LifeCycle.new({ prefix: 'logs-dev', date: Time.now + 24*60*60, enable: true })
+	
+
+To set your LifeCycle with this rules:
+
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host = "oss-cn-hangzhou.aliyuncs.com"
+    bucket = "bucket-name"
+    client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
+    
+    res = client.bucket_enable_lifecycle([rule1, rule2])	puts res.success?, res.headers
+
+### Get LifeCycle
+
+To get LifeCycle for bucket, use Client#bucket_get_lifecycle:
+
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host = "oss-cn-hangzhou.aliyuncs.com"
+    bucket = "bucket-name"
+    client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
+    
+    res = client.bucket_get_lifecycle
+    puts res.success?, res.parsed_response
+    
+
+### Disable LifeCycle
+
+
+With Client#bucket_disable_lifecycle, you can disable LifeCycle:
+
+
+    require 'aliyun/oss'
+    
+    access_key, secret_key = "your id", "your secret"
+    host = "oss-cn-hangzhou.aliyuncs.com"
+    bucket = "bucket-name"
+    client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
+    
+    res = client.bucket_disable_lifecycle
+    puts res.success?, res.headers
+    
+
+Next, Let's discuss about [Error](./error.md)        
+       

data/wiki/multipart.md

@@ -68,13 +68,13 @@ It can used to upload part to a object. Please note:
     bucket = "bucket-name"
     client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
     
-    part1 = Aliyun::Oss::Multipart::Part.new({ number: 1, etag: 'etag1' })
-	part2 = Aliyun::Oss::Multipart::Part.new({ number: 2, etag: 'etag2' })
-	part3 = Aliyun::Oss::Multipart::Part.new({ number: 3, etag: 'etag3' })
+    part1 = Aliyun::Oss::Struct::Part.new({ number: 1, etag: 'etag1' })
+	part2 = Aliyun::Oss::Struct::Part.new({ number: 2, etag: 'etag2' })
+	part3 = Aliyun::Oss::Struct::Part.new({ number: 3, etag: 'etag3' })
 	res = client.bucket_complete_multipart("Exciting-Ruby.mp4", "Upload ID", [part1, part2, part3])
 	
 
-Here, we create Aliyun::Oss::Multipart::Part to build your part, use Part#valid? to valid the object.
+Here, we create Aliyun::Oss::Struct::Part to build your part, use Part#valid? to valid the object.
 
 ### Abort Multipart Upload
 
@@ -121,5 +121,7 @@ Sometimes, you want to know which parts are uploaded.
     
     res = client.bucket_list_parts("Upload ID")
     puts res.success?, res.parsed_response
+
+
+OK, It's time to visit [CORS](./cors.md)    
     
-    

data/wiki/object.md

@@ -32,7 +32,7 @@ Client#bucket_create_object support file or bin data to upload.
     puts res.success?, res.headers
     
 
-The Upload limit Data to 5 GB, if large than it, use [Multipart Upload](./multipart.md).
+The Upload limit Data to 5 GB, if large than, visit [Multipart Upload](./multipart.md).
 
 
 ### Create a folder
@@ -49,12 +49,12 @@ To Create a folder, it's easy, just pass key with "/" at last:
     res = client.bucket_create_object("images/", "")
     puts res.success?, res.headers
 
-Create simulations folder nature created a size of 0 object.Uploads and downloads, for this object can only console to end with "/" object to display the folder. So the user can use this way to implement to create simulation folder. And access to the folder can see files below the folder.
+Create simulations folder nature created a object with size equals 0. Uploads and downloads, for this object can only console to end with "/" object to display the folder. So the user can use this way to implement to create simulation folder. And access to the folder can see files below the folder.
 
     
 ### Customize Http Header for object
 
-OSS service allow users to customize the http headers of object. The following code set the expiration time for the Object:
+OSS allow users to customize the http headers of object. The following code set the expiration time for the Object:
 
     require 'aliyun/oss'
     
@@ -64,15 +64,15 @@ OSS service allow users to customize the http headers of object. The following c
     client = Aliyun::Oss::Client.new(access_key, secret_key, host: host, bucket: bucket)
     
     file = File.new("path/to/image.png")
-    res = client.bucket_create_object("image.png", file, { 'Content-Type' => 'image/png', "Expires" => "Fri, 28 Feb 2012 05:38:42 GMT" })
+    res = client.bucket_create_object("image.png", file, { 'Content-Type' => 'image/png', "Expires" => "Sun, 25 Oct 2015 05:38:42 GMT" })
     puts res.success?, res.headers
  
-Except Expires, also support Cache-Control, Content-Disposition, Content-Encoding, Content-MD5, more details visit: [Client#bucket_create_object]().
+Except Expires, it also support Cache-Control, Content-Disposition, Content-Encoding, Content-MD5, more details visit: [Client#bucket_create_object](http://www.rubydoc.info/gems/aliyun-oss-sdk/Aliyun%2FOss%2FClient%3Abucket_create_object).
 
 
 ### Set User Meta
 
-OSS Support meta information for object.
+OSS Support set some user meta information for object. Here we set x-oss-meta-user to username for object:
 
     require 'aliyun/oss'
     
@@ -86,14 +86,14 @@ OSS Support meta information for object.
     puts res.success?, res.headers
 
 
-user meta is information with "x-oss-meta" stored in headers, the maxinum limit is 2KB.
+user meta information stored as headers with prefix: "x-oss-meta", the maxinum limit is 2KB for all meta information.
 
 Note: the user meta key is case-insensitive, but value is case-sensitive.
 
 
 ### Append Upload
 
-OSS Allow users to append data to a object, but only for appendable object, Objects created with Append Upload is Appendable object, Upload via simple upload is Normal object:
+OSS Allow users to append data to a object, but only for appendable object, Objects created with Append Upload is Appendable object, Upload via Simple Upload is Normal object:
 
 
     require 'aliyun/oss'
@@ -114,9 +114,11 @@ OSS Allow users to append data to a object, but only for appendable object, Obje
     res = client.bucket_append_object("secret.zip", "append information", position)
     puts res.success?, res.headers
     
-Users upload with Append mode, the important is to set position correctly. When a user creates an Appendable Object, additional position to 0. When the Appendable Object for additional content, additional location as the Object of the current length. There are two ways to get the Object length: one is through return after the upload additional content. Another is fetch by head object(Client#bucket_get_meta_object). the next position is store with header: x-oss-next-append.
+Users upload with Append mode, the most important is to set position correctly. When a user creates an Appendable Object, additional position to 0. When the Append additional content for Object, the postion is the current length of the object. There are two ways to get the Object length: one is through response after the append upload. Another is fetch with [Client#bucket_get_meta_object(http://www.rubydoc.info/gems/aliyun-oss-sdk/Aliyun/Oss/Client#bucket_get_meta_object-instance_method). the next position information is stored with key --- x-oss-next-append in headers.
+
+Note: You can set meta information only when create appendable object(the first append). Later, if you want to change the meta, use [Client#bucket_copy_object](http://www.rubydoc.info/gems/aliyun-oss-sdk/Aliyun%2FOss%2FClient%3Abucket_copy_object) -- set source and destination for the same Object.
+
 
-Note: Only when create the appendable object can set object meta. Later if you need to change the object meta, can use copy object interface(Client#bucket_copy_object) -- source and destination for the same Object.  
 
 ## List objects in Bucket
 
@@ -149,7 +151,8 @@ the method support many Parameters to get flexible results:
     res = client.bucket_list_objects(prefix: 'pic', delimiter: '/')
     puts res.success?, res.parsed_response
 
-It list results with prefix: pic and end with "/", for example: "pic-people/". More about the Paramters, visit: [Client#bucket_list_objects]()
+It list results with prefix: pic and end with "/", for example: "pic-people/". More about the Paramters, visit: [Client#bucket_list_objects](http://www.rubydoc.info/gems/aliyun-oss-sdk/Aliyun%2FOss%2FClient%3Abucket_list_objects)
+
 
 ### Get Object
 
@@ -163,7 +166,7 @@ It list results with prefix: pic and end with "/", for example: "pic-people/". M
     res = client.bucket_get_object('image.png')
     puts res.success?, res.parsed_response
     
-It Support much Parameters, Range, If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match. With Range, we can get data from a object, it's useful for download partly and so on.
+It Support Parameters, Range, If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match. With Range, we can get range data from a object, it's useful for download partly and so on.
 
     
 ### Get Meta Object
@@ -180,6 +183,7 @@ To get meta information of a object, use Client#get_meta_object:
     res = client.bucket_get_meta_object('image.png')
     puts res.success?, res.headers
 
+
 ### Delete Object
 
     require 'aliyun/oss'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aliyun-oss-sdk
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.1.0
 platform: ruby
 authors:
 - Newell Zhu
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2015-10-26 00:00:00.000000000 Z
+date: 2015-10-31 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: httparty
@@ -94,6 +94,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: pry-byebug
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: webmock
   requirement: !ruby/object:Gem::Requirement
@@ -122,6 +136,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: rubocop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 description: Aliyun OSS Ruby SDK
 email:
 - zlx.star@gmail.com
@@ -130,6 +158,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitignore"
+- ".rubocop.yml"
 - ".travis.yml"
 - Gemfile
 - LICENSE
@@ -141,12 +170,26 @@ files:
 - lib/aliyun/oss.rb
 - lib/aliyun/oss/authorization.rb
 - lib/aliyun/oss/client.rb
+- lib/aliyun/oss/client/bucket_multiparts.rb
+- lib/aliyun/oss/client/bucket_objects.rb
+- lib/aliyun/oss/client/buckets.rb
+- lib/aliyun/oss/client/clients.rb
+- lib/aliyun/oss/error.rb
 - lib/aliyun/oss/http.rb
-- lib/aliyun/oss/multipart/part.rb
-- lib/aliyun/oss/rule/cors.rb
-- lib/aliyun/oss/rule/lifecycle.rb
+- lib/aliyun/oss/struct.rb
+- lib/aliyun/oss/struct/bucket.rb
+- lib/aliyun/oss/struct/cors.rb
+- lib/aliyun/oss/struct/lifecycle.rb
+- lib/aliyun/oss/struct/logging.rb
+- lib/aliyun/oss/struct/multipart.rb
+- lib/aliyun/oss/struct/object.rb
+- lib/aliyun/oss/struct/part.rb
+- lib/aliyun/oss/struct/referer.rb
+- lib/aliyun/oss/struct/website.rb
 - lib/aliyun/oss/utils.rb
 - lib/aliyun/oss/version.rb
+- lib/aliyun/oss/xml_generator.rb
+- todo.md
 - wiki/bucket.md
 - wiki/cors.md
 - wiki/error.md
@@ -179,4 +222,3 @@ signing_key:
 specification_version: 4
 summary: Aliyun OSS Ruby SDK
 test_files: []
-has_rdoc: