vgs_api_client 0.0.1.alpha202204221804 → 0.0.1.alpha202204222331

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ad6f53cf37b26adf6ad0d2d8601bce2d3812dfd8f33f5956fb2bc7a1a0adedc6
-  data.tar.gz: b1f5add24e6548547ffacda7cde9ebf25f2db4fcbe7f350b2fa8836efe93544e
+  metadata.gz: accb9960204c2fb676b087b2058d010bb91ebf79f52b9b499c8274af88e3d504
+  data.tar.gz: '09fdb9b31c256659c5ec9ffc95d558e1998627b1c62daa9b290d01af65282c6d'
 SHA512:
-  metadata.gz: 0e24e515b39092e5027afa40defa1efb5c4162fbc9889118d9dcd114beb8b0fbdba030f181f4df81f7031d1e573f1743f2d7ed8e6e3057a255715c32bf91e967
-  data.tar.gz: d738f6848d1e2e61bd074319153ecd7dd8646efa59f428f103e86a208e54762d4e7921ad95090d530bfb1fb60725cf8e5f8f7c2978d3e0de05bc8dec1f0bd9c3
+  metadata.gz: 8d8b2df4b825a2e03715ab0213f447976f686b7109dc54873e37899d9225b3d88f21015c814ca3bcf17638be8334c3b20874801b5f40ea1a66f6e1100f9a12b7
+  data.tar.gz: 03601153f237e61f623bd99a425b4b854302855dd98907e34cf0dc054cf856c435899233aecfd11a8dfe798475bff66f54259d0b8f0cb18bda05e582223feae2

data/README.md

@@ -0,0 +1,33 @@
+# vgs-api-client-python
+
+This repository contains a Ruby API client library for the Very Good Security API.
+
+### Requirements
+
+Building and using the API client library requires Ruby 2.6+.
+
+### Installation
+
+```
+gem install vgs-api-client
+```
+
+### Development
+
+Follow [DEVELOPMENT](DEVELOPMENT.md) instruction.
+
+### Release
+
+Follow [RELEASE](RELEASE.md) instruction.
+
+### Documentation
+
+https://www.verygoodsecurity.com/docs/vault/api/
+
+### Tutorial
+
+https://www.verygoodsecurity.com/docs/tokenization/ruby-tutorial
+
+### Support
+
+support@verygoodsecurity.com

data/lib/{vgs_api_client → openapi_client}/api_client.rb

@@ -31,7 +31,7 @@ module VgsApiClient
     # @option config [Configuration] Configuration for initializing the object, default to Configuration.default
     def initialize(config = Configuration.default)
       @config = config
-      @user_agent = "vgs-api-client/0.0.1.alpha202204221804/ruby"
+      @user_agent = "vgs-api-client/0.0.1.alpha202204222331/ruby"
       @default_headers = {
         'Content-Type' => 'application/json',
         'User-Agent' => @user_agent

data/lib/{vgs_api_client → openapi_client}/version.rb

@@ -11,5 +11,5 @@ OpenAPI Generator version: 5.4.0
 =end
 
 module VgsApiClient
-  VERSION = '0.0.1.alpha202204221804'
+  VERSION = '0.0.1.alpha202204222331'
 end

data/lib/openapi_client.rb

@@ -0,0 +1,53 @@
+=begin
+#Vault HTTP API
+
+#The VGS Vault HTTP API is used for storing, retrieving, and managing sensitive data (aka Tokenization) within a VGS Vault.  The VGS API is organized around REST. Our API is built with a predictable resource-oriented structure, uses JSON-encoded requests and responses, follows standard HTTP verbs/responses, and uses industry standard authentication.  ## What is VGS  Storing sensitive data on your company’s infrastructure often comes with a heavy compliance burden. For instance, storing payments data yourself greatly increases the amount of work needed to become PCI compliant. It also increases your security risk in general. To combat this, companies will minimize the amount of sensitive information they have to handle or store.  VGS provides multiple methods for minimizing the sensitive information that needs to be stored which allows customers to secure any type of data for any use-case.  **Tokenization** is a method that focuses on securing the storage of data. This is the quickest way to get started and is free. [Get started with Tokenization](https://www.verygoodsecurity.com/docs/tokenization/getting-started).  **Zero Data** is a unique method invented by VGS in 2016 that securely stores data like Tokenization, however it also removes the customer’s environment from PCI scope completely providing maximum security, and minimum compliance scope. [Get started with Zero Data](https://www.verygoodsecurity.com/docs/getting-started/before-you-start).  Additionally, for scenarios where neither technology is a complete solution, for instance with legacy systems, VGS provides a compliance product which guarantees customers are able to meet their compliance needs no matter what may happen. [Get started with Control](https://www.verygoodsecurity.com/docs/control).  ## Learn about Tokenization  - [Create an Account for Free Tokenization](https://dashboard.verygoodsecurity.com/tokenization) - [Try a Tokenization Demo](https://www.verygoodsecurity.com/docs/tokenization/getting-started) - [Install a Tokenization SDK](https://www.verygoodsecurity.com/docs/tokenization/client-libraries)  ### Authentication  This API uses `Basic` authentication.  Credentials to access the API can be generated on the [dashboard](https://dashboard.verygoodsecurity.com) by going to the Settings section of the vault of your choosing.  [Docs » Guides » Access credentials](https://www.verygoodsecurity.com/docs/settings/access-credentials)  ## Resource Limits  ### Data Limits  This API allows storing data up to 32MB in size.  ### Rate Limiting  The API allows up to 3,000 requests per minute. Requests are associated with the vault, regardless of the access credentials used to authenticate the request.  Your current rate limit is included as HTTP headers in every API response:  | Header Name             | Description                                              | |-------------------------|----------------------------------------------------------| | `x-ratelimit-remaining` | The number of requests remaining in the 1-minute window. |  If you exceed the rate limit, the API will reject the request with HTTP [429 Too Many Requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429).  ### Errors  The API uses standard HTTP status codes to indicate whether the request succeeded or not.  In case of failure, the response body will be JSON in a predefined format. For example, trying to create too many aliases at once results in the following response:  ```json {     \"errors\": [         {             \"status\": 400,             \"title\": \"Bad request\",             \"detail\": \"Too many values (limit: 20)\",             \"href\": \"https://api.sandbox.verygoodvault.com/aliases\"         }     ] } ``` 
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@verygoodsecurity.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.4.0
+
+=end
+
+# Common files
+require 'openapi_client/api_client'
+require 'openapi_client/api_error'
+require 'openapi_client/version'
+require 'openapi_client/configuration'
+
+# Models
+require 'openapi_client/models/alias_format'
+require 'openapi_client/models/api_error'
+require 'openapi_client/models/create_aliases_request'
+require 'openapi_client/models/create_aliases_request_new'
+require 'openapi_client/models/create_aliases_request_reference'
+require 'openapi_client/models/inline_response200'
+require 'openapi_client/models/inline_response2001'
+require 'openapi_client/models/inline_response201'
+require 'openapi_client/models/inline_response_default'
+require 'openapi_client/models/model_alias'
+require 'openapi_client/models/revealed_data'
+require 'openapi_client/models/update_alias_request'
+require 'openapi_client/models/update_alias_request_data'
+
+# APIs
+require 'openapi_client/api/aliases_api'
+
+module VgsApiClient
+  class << self
+    # Customize default settings for the SDK using block.
+    #   VgsApiClient.configure do |config|
+    #     config.username = "xxx"
+    #     config.password = "xxx"
+    #   end
+    # If no block given, return the default Configuration object.
+    def configure
+      if block_given?
+        yield(Configuration.default)
+      else
+        Configuration.default
+      end
+    end
+  end
+end

data/lib/version.rb

@@ -1,3 +1,3 @@
 module VGS
-  VERSION = '0.0.1.alpha202204221804'
+  VERSION = '0.0.1.alpha202204222331'
 end

data/lib/vgs_api_client.rb

@@ -1,26 +1,4 @@
-# Common files
-require 'vgs_api_client/api_client'
-require 'vgs_api_client/api_error'
-require 'vgs_api_client/version'
-require 'vgs_api_client/configuration'
-
-# Models
-require 'vgs_api_client/models/alias_format'
-require 'vgs_api_client/models/api_error'
-require 'vgs_api_client/models/create_aliases_request'
-require 'vgs_api_client/models/create_aliases_request_new'
-require 'vgs_api_client/models/create_aliases_request_reference'
-require 'vgs_api_client/models/inline_response200'
-require 'vgs_api_client/models/inline_response2001'
-require 'vgs_api_client/models/inline_response201'
-require 'vgs_api_client/models/inline_response_default'
-require 'vgs_api_client/models/model_alias'
-require 'vgs_api_client/models/revealed_data'
-require 'vgs_api_client/models/update_alias_request'
-require 'vgs_api_client/models/update_alias_request_data'
-
-# APIs
-require 'vgs_api_client/api/aliases_api'
+require 'openapi_client'
 
 module VGS
   class VgsApiException < StandardError

data/openapi_client.gemspec

@@ -0,0 +1,38 @@
+# -*- encoding: utf-8 -*-
+
+=begin
+#Vault HTTP API
+
+#The VGS Vault HTTP API is used for storing, retrieving, and managing sensitive data (aka Tokenization) within a VGS Vault.  The VGS API is organized around REST. Our API is built with a predictable resource-oriented structure, uses JSON-encoded requests and responses, follows standard HTTP verbs/responses, and uses industry standard authentication.  ## What is VGS  Storing sensitive data on your company’s infrastructure often comes with a heavy compliance burden. For instance, storing payments data yourself greatly increases the amount of work needed to become PCI compliant. It also increases your security risk in general. To combat this, companies will minimize the amount of sensitive information they have to handle or store.  VGS provides multiple methods for minimizing the sensitive information that needs to be stored which allows customers to secure any type of data for any use-case.  **Tokenization** is a method that focuses on securing the storage of data. This is the quickest way to get started and is free. [Get started with Tokenization](https://www.verygoodsecurity.com/docs/tokenization/getting-started).  **Zero Data** is a unique method invented by VGS in 2016 that securely stores data like Tokenization, however it also removes the customer’s environment from PCI scope completely providing maximum security, and minimum compliance scope. [Get started with Zero Data](https://www.verygoodsecurity.com/docs/getting-started/before-you-start).  Additionally, for scenarios where neither technology is a complete solution, for instance with legacy systems, VGS provides a compliance product which guarantees customers are able to meet their compliance needs no matter what may happen. [Get started with Control](https://www.verygoodsecurity.com/docs/control).  ## Learn about Tokenization  - [Create an Account for Free Tokenization](https://dashboard.verygoodsecurity.com/tokenization) - [Try a Tokenization Demo](https://www.verygoodsecurity.com/docs/tokenization/getting-started) - [Install a Tokenization SDK](https://www.verygoodsecurity.com/docs/tokenization/client-libraries)  ### Authentication  This API uses `Basic` authentication.  Credentials to access the API can be generated on the [dashboard](https://dashboard.verygoodsecurity.com) by going to the Settings section of the vault of your choosing.  [Docs » Guides » Access credentials](https://www.verygoodsecurity.com/docs/settings/access-credentials)  ## Resource Limits  ### Data Limits  This API allows storing data up to 32MB in size.  ### Rate Limiting  The API allows up to 3,000 requests per minute. Requests are associated with the vault, regardless of the access credentials used to authenticate the request.  Your current rate limit is included as HTTP headers in every API response:  | Header Name             | Description                                              | |-------------------------|----------------------------------------------------------| | `x-ratelimit-remaining` | The number of requests remaining in the 1-minute window. |  If you exceed the rate limit, the API will reject the request with HTTP [429 Too Many Requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429).  ### Errors  The API uses standard HTTP status codes to indicate whether the request succeeded or not.  In case of failure, the response body will be JSON in a predefined format. For example, trying to create too many aliases at once results in the following response:  ```json {     \"errors\": [         {             \"status\": 400,             \"title\": \"Bad request\",             \"detail\": \"Too many values (limit: 20)\",             \"href\": \"https://api.sandbox.verygoodvault.com/aliases\"         }     ] } ``` 
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@verygoodsecurity.com
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.4.0
+
+=end
+
+$:.push File.expand_path("../lib", __FILE__)
+require "openapi_client/version"
+
+Gem::Specification.new do |s|
+  s.name        = "openapi_client"
+  s.version     = VgsApiClient::VERSION
+  s.platform    = Gem::Platform::RUBY
+  s.authors     = ["Very Good Security"]
+  s.email       = ["support@verygoodsecurity.com"]
+  s.homepage    = "https://openapi-generator.tech"
+  s.summary     = "VGS Vault API"
+  s.description = "This gem maps to VGS Vault API"
+  s.license     = "Unlicense"
+  s.required_ruby_version = ">= 2.4"
+
+  s.add_runtime_dependency 'typhoeus', '~> 1.0', '>= 1.0.1'
+
+  s.add_development_dependency 'rspec', '~> 3.6', '>= 3.6.0'
+
+  s.files         = `find *`.split("\n").uniq.sort.select { |f| !f.empty? }
+  s.test_files    = `find spec/*`.split("\n")
+  s.executables   = []
+  s.require_paths = ["lib"]
+end

data/scripts/assemble/run.sh

@@ -1,9 +1,9 @@
 #!/bin/bash
 
-LIB_VERSION=${LIB_VERSION:-0.0.1.alpha202204221804.alpha$(date "+%Y%m%d%H%M")}
+LIB_VERSION=${LIB_VERSION:-0.0.1.alpha$(date "+%Y%m%d%H%M")}
 
 # fix version
-grep -rl 0.0.1.alpha202204221804 . | xargs sed -i "s/0.0.1.alpha202204221804/${LIB_VERSION}/g"
+grep -rl 0.0.1.alpha202204222331 . | xargs sed -i "s/0.0.1.alpha202204222331/${LIB_VERSION}/g"
 
 # build
 gem build vgs_api_client.gemspec

data/scripts/publish/run.sh

@@ -6,7 +6,7 @@ usage() { echo "Required env var '$1' is missing"; exit 1; }
 
 [ -z "${ARTIFACT_REPOSITORY_TOKEN}" ] && usage "ARTIFACT_REPOSITORY_TOKEN" ;
 
-LIB_VERSION=${LIB_VERSION:-0.0.1.alpha202204221804.alpha$(date "+%Y%m%d%H%M")}
+LIB_VERSION=${LIB_VERSION:-0.0.1.alpha$(date "+%Y%m%d%H%M")}
 
 mkdir ~/.gem
 echo ":rubygems_api_key: ${ARTIFACT_REPOSITORY_TOKEN}" > ~/.gem/credentials

data/scripts/publish.sh

@@ -6,7 +6,7 @@ usage() { echo "Required env var '$1' is missing"; exit 1; }
 
 [ -z "${ARTIFACT_REPOSITORY_TOKEN}" ] && usage "ARTIFACT_REPOSITORY_TOKEN" ;
 
-export LIB_VERSION=${LIB_VERSION:-0.0.1.alpha202204221804.alpha$(date "+%Y%m%d%H%M")}
+export LIB_VERSION=${LIB_VERSION:-0.0.1.alpha$(date "+%Y%m%d%H%M")}
 
 docker-compose build && \
 docker-compose run assemble && \

data/scripts/run-tests-e2e.sh

@@ -2,7 +2,7 @@
 
 set -e
 
-export LIB_VERSION=${LIB_VERSION:-0.0.1.alpha202204221804.alpha$(date "+%Y%m%d%H%M")}
+export LIB_VERSION=${LIB_VERSION:-0.0.1.alpha$(date "+%Y%m%d%H%M")}
 
 docker-compose build test-e2e && \
 docker-compose run test-e2e

data/scripts/test/run.sh

@@ -4,8 +4,8 @@ set -e
 
 echo "Installing lib from local sources"
 # fix version
-VERSION=0.0.1.alpha202204221804.alpha$(date "+%Y%m%d%H%M")
-grep -rl 0.0.1.alpha202204221804 . | xargs sed -i "s/0.0.1.alpha202204221804/$VERSION/g"
+VERSION=0.0.1.alpha$(date "+%Y%m%d%H%M")
+grep -rl 0.0.1.alpha202204222331 . | xargs sed -i "s/0.0.1.alpha202204222331/$VERSION/g"
 
 bundle install
 

data/spec/spec_helper.rb

@@ -11,7 +11,7 @@ OpenAPI Generator version: 5.4.0
 =end
 
 # load the gem
-require 'vgs_api_client'
+require 'openapi_client'
 
 # The following  was generated by the `rspec --init` command. Conventionally, all
 # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.

data/spec/test_aliases_api_spec.rb

@@ -4,26 +4,24 @@ require 'vgs_api_client'
 
 describe 'AliasesApiSpec' do
   before(:all) do
-    config = VGS.config(username = ENV["VAULT_API_USERNAME"], password = ENV["VAULT_API_PASSWORD"])
-    @aliases_api = VGS::Aliases.new(config)
+    config = VGS.config(username = ENV['VAULT_API_USERNAME'], password = ENV['VAULT_API_PASSWORD'])
+    @aliases_api = VGS::Aliases.new config
   end
 
   describe 'redact' do
     it 'should redact values' do
-      data = [
-        {
-          :format => 'UUID',
-          :value => '5201784564572092',
-          :classifiers => %w[credit-card number],
-          :storage => 'PERSISTENT',
-        },
-        {
-          :format => 'UUID',
-          :value => 'Joe Doe',
-          :storage => 'VOLATILE',
-        }
-      ]
-      aliases = @aliases_api.redact(data)
+      data = [{
+                format: 'UUID',
+                value: '5201784564572092',
+                classifiers: %w[credit-card number],
+                storage: 'PERSISTENT'
+              },
+              {
+                format: 'UUID',
+                value: 'Joe Doe',
+                storage: 'VOLATILE'
+              }]
+      aliases = @aliases_api.redact data
       expect(aliases.length).to eq 2
       data.each_with_index do |item, index|
         expect(aliases[index].value).to eq item[:value]
@@ -37,22 +35,20 @@ describe 'AliasesApiSpec' do
 
   describe 'reveal' do
     it 'should reveal aliases' do
-      data = [
-        {
-          :format => 'UUID',
-          :value => '5201784564572092',
-          :classifiers => %w[credit-card number],
-          :storage => 'PERSISTENT',
-        },
-        {
-          :format => 'UUID',
-          :value => 'Joe Doe',
-          :storage => 'VOLATILE',
-        }
-      ]
+      data = [{
+                format: 'UUID',
+                value: '5201784564572092',
+                classifiers: %w[credit-card number],
+                storage: 'PERSISTENT'
+              },
+              {
+                format: 'UUID',
+                value: 'Joe Doe',
+                storage: 'VOLATILE'
+              }]
       aliases = @aliases_api.redact(data).map { |item| item.aliases[0]._alias }
 
-      response = @aliases_api.reveal(aliases)
+      response = @aliases_api.reveal aliases
 
       expect(response.length).to eq 2
       original_values = data.map { |i| i[:value] }
@@ -63,15 +59,13 @@ describe 'AliasesApiSpec' do
 
   describe 'update' do
     it 'should update alias' do
-      data = [
-        {
-          :format => 'UUID',
-          :value => SecureRandom.alphanumeric(10),
-        }
-      ]
+      data = [{
+                format: 'UUID',
+                value: SecureRandom.alphanumeric(10)
+              }]
       _alias = @aliases_api.redact(data).map { |item| item.aliases[0]._alias }[0]
 
-      @aliases_api.update(_alias = _alias, data = { :classifiers => ["secure"] })
+      @aliases_api.update _alias, classifiers: %w[secure]
 
       response = @aliases_api.reveal(_alias)
       expect(response[_alias].classifiers).to eq %w[secure]
@@ -80,15 +74,13 @@ describe 'AliasesApiSpec' do
 
   describe 'delete' do
     it 'should delete alias' do
-      data = [
-        {
-          :format => 'UUID',
-          :value => '5201784564572092',
-        }
-      ]
+      data = [{
+                format: 'UUID',
+                value: '5201784564572092'
+              }]
       _alias = @aliases_api.redact(data).map { |item| item.aliases[0]._alias }[0]
 
-      @aliases_api.delete(_alias = _alias)
+      @aliases_api.delete _alias
 
       expect { @aliases_api.reveal(_alias) }.to raise_error(VGS::VgsApiException)
     end

data/vgs_api_client.gemspec

@@ -11,8 +11,8 @@ Gem::Specification.new do |s|
   s.homepage    = "https://github.com/verygoodsecurity/vgs-api-client-ruby"
   s.summary     = "VGS API Client"
   s.description = "This gem maps to VGS Vault API"
-  s.license     = "BSD"
-  s.required_ruby_version = ">= 2.4"
+  s.license     = "BSD 3-Clause Clear License"
+  s.required_ruby_version = ">= 2.6"
 
   s.metadata = {
     "homepage_uri"      => "https://www.verygoodsecurity.com",

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vgs_api_client
 version: !ruby/object:Gem::Version
-  version: 0.0.1.alpha202204221804
+  version: 0.0.1.alpha202204222331
 platform: ruby
 authors:
 - Very Good Security
@@ -59,32 +59,33 @@ extra_rdoc_files: []
 files:
 - DEVELOPMENT.md
 - Gemfile
-- Gemfile.lock
 - LICENSE
+- README.md
 - RELEASE.md
 - Rakefile
-- datadog.rb
 - docker-compose.yaml
+- lib/openapi_client.rb
+- lib/openapi_client/api/aliases_api.rb
+- lib/openapi_client/api_client.rb
+- lib/openapi_client/api_error.rb
+- lib/openapi_client/configuration.rb
+- lib/openapi_client/models/alias_format.rb
+- lib/openapi_client/models/api_error.rb
+- lib/openapi_client/models/create_aliases_request.rb
+- lib/openapi_client/models/create_aliases_request_new.rb
+- lib/openapi_client/models/create_aliases_request_reference.rb
+- lib/openapi_client/models/inline_response200.rb
+- lib/openapi_client/models/inline_response2001.rb
+- lib/openapi_client/models/inline_response201.rb
+- lib/openapi_client/models/inline_response_default.rb
+- lib/openapi_client/models/model_alias.rb
+- lib/openapi_client/models/revealed_data.rb
+- lib/openapi_client/models/update_alias_request.rb
+- lib/openapi_client/models/update_alias_request_data.rb
+- lib/openapi_client/version.rb
 - lib/version.rb
 - lib/vgs_api_client.rb
-- lib/vgs_api_client/api/aliases_api.rb
-- lib/vgs_api_client/api_client.rb
-- lib/vgs_api_client/api_error.rb
-- lib/vgs_api_client/configuration.rb
-- lib/vgs_api_client/models/alias_format.rb
-- lib/vgs_api_client/models/api_error.rb
-- lib/vgs_api_client/models/create_aliases_request.rb
-- lib/vgs_api_client/models/create_aliases_request_new.rb
-- lib/vgs_api_client/models/create_aliases_request_reference.rb
-- lib/vgs_api_client/models/inline_response200.rb
-- lib/vgs_api_client/models/inline_response2001.rb
-- lib/vgs_api_client/models/inline_response201.rb
-- lib/vgs_api_client/models/inline_response_default.rb
-- lib/vgs_api_client/models/model_alias.rb
-- lib/vgs_api_client/models/revealed_data.rb
-- lib/vgs_api_client/models/update_alias_request.rb
-- lib/vgs_api_client/models/update_alias_request_data.rb
-- lib/vgs_api_client/version.rb
+- openapi_client.gemspec
 - scripts/assemble/Dockerfile
 - scripts/assemble/run.sh
 - scripts/publish.sh
@@ -100,11 +101,10 @@ files:
 - spec/configuration_spec.rb
 - spec/spec_helper.rb
 - spec/test_aliases_api_spec.rb
-- test.rb
 - vgs_api_client.gemspec
 homepage: https://github.com/verygoodsecurity/vgs-api-client-ruby
 licenses:
-- BSD
+- BSD 3-Clause Clear License
 metadata:
   homepage_uri: https://www.verygoodsecurity.com
   bug_tracker_uri: https://github.com/verygoodsecurity/vgs-api-client-ruby/issues
@@ -118,7 +118,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.4'
+      version: '2.6'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">"

data/Gemfile.lock

@@ -1,70 +0,0 @@
-PATH
-  remote: .
-  specs:
-    vgs_api_client (0.0.1.alpha202204221804)
-      typhoeus (~> 1.0, >= 1.0.1)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    ast (2.4.2)
-    byebug (11.1.3)
-    coderay (1.1.3)
-    diff-lcs (1.5.0)
-    ethon (0.15.0)
-      ffi (>= 1.15.0)
-    ffi (1.15.5)
-    jaro_winkler (1.5.4)
-    method_source (1.0.0)
-    parallel (1.22.1)
-    parser (3.1.2.0)
-      ast (~> 2.4.1)
-    pry (0.13.1)
-      coderay (~> 1.1)
-      method_source (~> 1.0)
-    pry-byebug (3.9.0)
-      byebug (~> 11.0)
-      pry (~> 0.13.0)
-    psych (4.0.3)
-      stringio
-    rainbow (3.1.1)
-    rake (13.0.6)
-    rspec (3.11.0)
-      rspec-core (~> 3.11.0)
-      rspec-expectations (~> 3.11.0)
-      rspec-mocks (~> 3.11.0)
-    rspec-core (3.11.0)
-      rspec-support (~> 3.11.0)
-    rspec-expectations (3.11.0)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.11.0)
-    rspec-mocks (3.11.1)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.11.0)
-    rspec-support (3.11.0)
-    rubocop (0.66.0)
-      jaro_winkler (~> 1.5.1)
-      parallel (~> 1.10)
-      parser (>= 2.5, != 2.5.1.1)
-      psych (>= 3.1.0)
-      rainbow (>= 2.2.2, < 4.0)
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (>= 1.4.0, < 1.6)
-    ruby-progressbar (1.11.0)
-    stringio (3.0.1)
-    typhoeus (1.4.0)
-      ethon (>= 0.9.0)
-    unicode-display_width (1.5.0)
-
-PLATFORMS
-  x86_64-darwin-21
-
-DEPENDENCIES
-  pry-byebug
-  rake (~> 13.0.1)
-  rspec (~> 3.6, >= 3.6.0)
-  rubocop (~> 0.66.0)
-  vgs_api_client!
-
-BUNDLED WITH
-   2.3.11

data/datadog.rb

@@ -1,10 +0,0 @@
-require 'datadog_api_client'
-
-api_instance = DatadogAPIClient::V1::IPRangesAPI.new
-
-begin
-  result = api_instance.get_ip_ranges
-  p result
-rescue DatadogAPIClient::V1::APIError => e
-  puts "Error when calling IPRangesAPI->get_ip_ranges: #{e}"
-end

data/test.rb

@@ -1,93 +0,0 @@
-require 'vgs'
-
-# Defining the host is optional and defaults to https://api.sandbox.verygoodvault.com.
-# For production use https://api.live.verygoodvault.com
-config = VGS.config(
-  host = "https://api.sandbox.verygoodvault.com",
-  username = ENV["VAULT_API_USERNAME"],
-  password = ENV["VAULT_API_PASSWORD"]
-)
-
-# in this example we are storing three tokens within your VGS vault using a single API call
-# this will return three tokens which can be stored in your system and used individually or together
-# through any VGS Vault product including our Zero Data platform.
-#
-# the aliases namespace allows you to directly store, manage, and
-# retrieve tokens from your vgs vault.
-#
-# in the below example we demonstrate how to store payment card and personally identifiable
-# information in a single API call.
-#
-# see https://www.verygoodsecurity.com/docs/vault/what-is-zero-data
-# to learn how to remove any servers handling sentistive information
-# 100% from pci scope.
-
-api = VGS::Aliases.new(config)
-
-# first, let's create a request payload to tokenize our sensitive data.
-data = [
-  # credit card
-  dict(
-    # format is used to determine how the stored token is represented
-    # see https://www.verygoodsecurity.com/docs/terminology/nomenclature#alias-formats
-    # to learn about different formats and representations available
-    # to tokenize secured data.
-    :format => "PFPT",
-    :value => "4111111111111111",
-    # see https://www.verygoodsecurity.com/docs/vault/concepts#classifiers
-    # to learn how to classify and tag your data to help secure access and
-    # route data compliantly.
-    :classifiers => ["credit-card", "number"],
-    :storage => "PERSISTENT"
-  ),
-  # card security code
-  dict(
-    :format => "UUID",
-    :value => "123",
-    :classifiers => ["credit-card", "csc"],
-    # learn how volatile storage allows you to maintain full pci compliance
-    # https://www.verygoodsecurity.com/docs/terminology/nomenclature#storage
-    :storage => "VOLATILE"
-  ),
-  # social security number
-  dict(
-    :format => "UUID",
-    :value => "078-05-1120",
-    :classifiers => ["pii", "ssn"]
-  )
-]
-puts "Tokenizing multiple values..."
-
-aliases = api.redact(data)
-
-puts "Tokens created #{aliases}"
-
-# example of how to find the alias associated to each value
-puts aliases.map { |record| record.aliases[0]._alias }
-
-
-# next, let's update the classifiers and re-alias
-first_alias = aliases[0].aliases[0]._alias
-
-api.update(first_alias, { :classifiers => ["bank-account", "test-tag"] })
-
-puts "Token #{first_alias} updated"
-
-# now let's retrieve it back
-revealed = api.reveal(first_alias)
-
-puts "Token #{first_alias} retrieved\n{revealed}"
-
-# finally, let's delete an alias
-api.delete(first_alias)
-
-puts "Token #{first_alias} deleted"
-
-# now let's fetch it back to ensure it's not usable.
-puts "Trying to retrieve deleted token #{first_alias}..."
-begin
-  api.reveal(first_alias)
-rescue => error
-  puts "We can no longer fetch the token, it has been deleted: #{error.message}"
-end
-