QingStor::SDK

The official QingStor SDK for Ruby programming language.

This Gem uses Ruby's keyword arguments feature, thus Ruby v2.1.5 or higher is required. See this article for more details about keyword arguments.

Notice: As of sdk v2.4, we no longer support Ruby 2.4 and earlier versions since Ruby 2.4 has been marked as EOL. If you are still using Ruby 2.4 and earlier, you may not be able to use some new features of our sdk, so please upgrade your version of Ruby as soon as possible.

$ gem install qingstor-sdk

Specify qingstor-sdk as dependency in your application's Gemfile:

gem 'qingstor-sdk'

Ensure qingstor-sdk is installed as dependency with bundle install:

$ bundle install

Get code from GitHub:

$ git clone git@github.com:yunify/qingstor-sdk-ruby.git

Build and install with bundler:

$ cd qingstor-sdk-ruby
$ bundle install
$ bundle exec rake install

$ gem uninstall qingstor-sdk

Before using the SDK, please make sure you already have QingCloud API access key, apply one from QingCloud Console otherwise.

API Access Key Example:

access_key_id: 'ACCESS_KEY_ID_EXAMPLE'
secret_access_key: 'SECRET_ACCESS_KEY_EXAMPLE'

require 'qingstor/sdk'
require 'digest/md5'

# Create a config object with access_key_id and secret_access_key defined as
# environment variables.
config = QingStor::SDK::Config.init ENV['ENV_ACCESS_KEY_ID'],
                                    ENV['ENV_SECRET_ACCESS_KEY']

# Initialize QingStor service with the config object.
qs_service = QingStor::SDK::Service.new config

# List buckets
result = qs_service.list_buckets
# Print HTTP status code
puts result[:status_code]
# Print bucket count
puts result[:buckets].length
# Print the first bucket name
puts result[:buckets][0][:name]

# Initialize a QingStor bucket
bucket = qs_service.bucket 'test-bucket', 'pek3a'

# List objects
result = bucket.list_objects
# Print HTTP status code
puts result[:status_code]
# Print keys count
puts result[:keys].length


# Upload an object
file_path = File.expand_path '~/Desktop/Screenshot.jpg'
md5_string = Digest::MD5.file(file_path).to_s
result = bucket.put_object 'Screenshot.jpg',
                           content_md5: md5_string,
                           body:        File.open(file_path)
# Print HTTP status code.
puts result[:status_code]

Except access_key_id and secret_access_key, you can also configure the API server (in case of QingStor is deployed in private environment, thus has different endpoint with public QingStor) either in the config file, or in the program dynamically.

Notice: config will not be checked available when new, load and update, which will be done right before initializing service or bucket. If you need to check config, you should call config.check whenever you want. If check failed, a ConfigurationError will be raised.

Code Example:

require 'qingstor/sdk'

# Load default configuration
config = QingStor::SDK::Config.new.load_default_config

# Create with default value
# priority from high to low: param > env > user config > default config
config = QingStor::SDK::Config.new({
  host:      'qingstor.dev',
  log_level: 'debug',
})

# Create a configuration from AccessKeyID and SecretAccessKey
config = QingStor::SDK::Config.init ENV['ENV_ACCESS_KEY_ID'],
                                    ENV['ENV_SECRET_ACCESS_KEY']

# Load configuration from config file
config = QingStor::SDK::Config.new
config = config.load_config_from_file '~/qingstor/config.yaml'

# Load configuration from env variable:
# QINGSTOR_ACCESS_KEY_ID for access_key_id
# QINGSTOR_SECRET_ACCESS_KEY for secret_access_key
# QINGSTOR_ENABLE_VIRTUAL_HOST_STYLE for enable_virtual_host_style
# QINGSTOR_ENDPOINT for endpoint
config = QingStor::SDK::Config.new.load_env_config

# Change API server
config.update({host: 'test.qingstor.com'})

Default Configuration File:

# QingStor services configuration

access_key_id: 'ACCESS_KEY_ID'
secret_access_key: 'SECRET_ACCESS_KEY'

host: 'qingstor.com'
port: 443
protocol: 'https'
# or set endpoint directly
# endpoint: https://qingstor.com:443

connection_retries: 3

# Additional User-Agent
additional_user_agent: ""

# Valid log levels are "debug", "info", "warn", "error", and "fatal".
log_level: warn

# SDK will use virtual host style for all API calls if enabled
enable_virtual_host_style: false

All notable changes to QingStor SDK for Ruby will be documented here.

• config: Add env variable support (#52)
• signer: Add support for anonymous API call (#53)
• config: Add support for endpoint (#55)
• config: Add support for enable_vhost_style (#56)

• Request: Modify Metadata in header to apply rfc 02 (#49)
• config: Refactor config check (#54)

• Support to set x-qs-metadata-directive header (#29)
• Add support for bucket replication (#45)

• ci: Transfer ci into github action (#30)

• Fix metadata added into signature when empty (#44)

• Add support for lifecycle and notification.
• Add support for bucket logging, bucket cname and append object. (#24)

• Modify content-type check for application/json. (#21)
• Fix sub-resources not be recognized when generate signature. (#25)
• Fix meta data not work as intended. (#26)
• Reverse fix of empty map in template, should not compact empty hash when sign. (#28)

• Fix status code of DELETE CORS API.

• Resource is not mandatory in bucket policy statement.

• Allow user to append additional info to User-Agent.

• Add ListMultipartUploads API.

• Fix request builder & signer.

• Fix signer bug.

• Fix signer bug.
• Add more parameters to sign.

• Add request parameters for GET Object.
• Add IP address conditions for bucket policy.

• Improve the implementation of deleting multiple objects.

• QingStor SDK for the Ruby programming language.

• QingStor Documentation
• QingStor Guide
• QingStor APIs

1. Fork it ( https://github.com/yunify/qingstor-sdk-ruby/fork )
2. Create your feature branch (git checkout -b new-feature)
3. Commit your changes (git commit -asm 'Add some feature')
4. Push to the branch (git push origin new-feature)
5. Create a new Pull Request

The Apache License (Version 2.0, January 2004).