vgs_api_client 0.0.1.alpha202401251923 → 0.0.1.dev202204182306

data/scripts/test/run.sh

@@ -1,13 +1,30 @@
-#!/usr/bin/env bash
+#!/usr/bin/env sh
 
 set -e
 
-echo "Installing lib from local sources"
-# fix version
-VERSION=0.0.1.alpha$(date "+%Y%m%d%H%M")
-grep -rl 0.0.1.alpha202401251923 . | xargs sed -i "s/0.0.1.alpha202401251923/$VERSION/g"
+#if [[ -n "$TEST_AGAINST_PUBLISHED_LIB_VERSION" ]]; then
+#    echo "Installing lib from PyPI ${TEST_AGAINST_PUBLISHED_LIB_VERSION} ..."
+#
+#  set +e
+#  ATTEMPT=1
+#  while [  $ATTEMPT -lt 60 ]; do
+#    echo "Attempt ${ATTEMPT} ..."
+#
+#    pip install vgs-api-client==${TEST_AGAINST_PUBLISHED_LIB_VERSION}
+#
+#    if [[ $? == 0 ]]; then
+#      echo "Installed ${TEST_AGAINST_PUBLISHED_LIB_VERSION}"
+#      break
+#    fi
+#
+#    ATTEMPT=$((ATTEMPT+1))
+#
+#    sleep 5
+#  done
+#  set -e
+#else
+  echo "Installing lib from local sources"
+  bundle install
+#fi
 
-bundle install
-
-echo "Running tests"
-bundle exec rspec -f documentation ./spec/*.rb
+bundle exec rspec ./spec/test_api_spec.rb

data/spec/api_client_spec.rb

@@ -1,7 +1,7 @@
 =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 and is implemented using industry best practices to ensure the security of the connection. Read more about [Identity and Access Management at VGS](https://www.verygoodsecurity.com/docs/vault/the-platform/iam)  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 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

data/spec/configuration_spec.rb

@@ -1,7 +1,7 @@
 =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 and is implemented using industry best practices to ensure the security of the connection. Read more about [Identity and Access Management at VGS](https://www.verygoodsecurity.com/docs/vault/the-platform/iam)  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 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

data/spec/spec_helper.rb

@@ -1,7 +1,7 @@
 =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 and is implemented using industry best practices to ensure the security of the connection. Read more about [Identity and Access Management at VGS](https://www.verygoodsecurity.com/docs/vault/the-platform/iam)  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 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
@@ -11,7 +11,7 @@ OpenAPI Generator version: 5.4.0
 =end
 
 # load the gem
-require 'openapi_client'
+require 'vgs_api_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_api_spec.rb

@@ -0,0 +1,97 @@
+require 'spec_helper'
+require 'securerandom'
+require 'vgs'
+
+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)
+  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)
+      expect(aliases.length).to eq 2
+      data.each_with_index do |item, index|
+        expect(aliases[index].value).to eq item[:value]
+        expect(aliases[index].storage).to eq item[:storage]
+        expect(aliases[index].aliases[0]._alias).to start_with "tok_"
+      end
+      expect(Set.new(aliases[0].classifiers)).to eq Set.new(%w[credit-card number])
+      expect(Set.new(aliases[1].classifiers)).to eq Set.new
+    end
+  end
+
+  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',
+        }
+      ]
+      aliases = @aliases_api.redact(data).map { |item| item.aliases[0]._alias }
+
+      response = @aliases_api.reveal(aliases)
+
+      expect(response.length).to eq 2
+      original_values = data.map { |i| i[:value] }
+      revealed_values = response.values.map { |i| i.value }
+      expect(Set.new(original_values)).to eq Set.new(revealed_values)
+    end
+  end
+
+  describe 'update' do
+    it 'should update alias' do
+      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"] })
+
+      response = @aliases_api.reveal(_alias)
+      expect(response[_alias].classifiers).to eq %w[secure]
+    end
+  end
+
+  describe 'delete' do
+    it 'should delete alias' do
+      data = [
+        {
+          :format => 'UUID',
+          :value => '5201784564572092',
+        }
+      ]
+      _alias = @aliases_api.redact(data).map { |item| item.aliases[0]._alias }[0]
+
+      @aliases_api.delete(_alias = _alias)
+
+      expect { @aliases_api.reveal(_alias) }.to raise_error(VGS::VgsApiException)
+    end
+  end
+
+end

data/vgs_api_client.gemspec

@@ -1,25 +1,31 @@
 # -*- encoding: utf-8 -*-
 
-require_relative "lib/version"
+=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 "vgs_api_client/version"
 
 Gem::Specification.new do |s|
   s.name        = "vgs_api_client"
-  s.version     = VGS::VERSION
+  s.version     = VgsApiClient::VERSION
   s.platform    = Gem::Platform::RUBY
   s.authors     = ["Very Good Security"]
-  s.email       = ["support@verygoodsecurity.com"]
-  s.homepage    = "https://github.com/verygoodsecurity/vgs-api-client-ruby"
-  s.summary     = "Very Good Security API Client"
-  s.description = "Very Good Security API Client library. More details on https://www.verygoodsecurity.com/"
-  s.license     = "BSD-3-Clause"
-  s.required_ruby_version = ">= 2.6"
-
-  s.metadata = {
-    "homepage_uri"      => "https://www.verygoodsecurity.com",
-    "bug_tracker_uri"   => "https://github.com/verygoodsecurity/vgs-api-client-ruby/issues",
-    "documentation_uri" => "https://www.verygoodsecurity.com/docs",
-    "source_code_uri"   => "https://github.com/verygoodsecurity/vgs-api-client-ruby"
-  }
+  s.email       = ["dev@verygoodsecurity.com"]
+  s.homepage    = "https://openapi-generator.tech"
+  s.summary     = "A ruby wrapper for the 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'
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vgs_api_client
 version: !ruby/object:Gem::Version
-  version: 0.0.1.alpha202401251923
+  version: 0.0.1.dev202204182306
 platform: ruby
 authors:
 - Very Good Security
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-01-25 00:00:00.000000000 Z
+date: 2022-04-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: typhoeus
@@ -50,70 +50,59 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 3.6.0
-description: Very Good Security API Client library. More details on https://www.verygoodsecurity.com/
+description: This gem maps to VGS Vault API
 email:
-- support@verygoodsecurity.com
+- dev@verygoodsecurity.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
 - DEVELOPMENT.md
 - Gemfile
+- Gemfile.lock
 - LICENSE
-- README.md
 - RELEASE.md
 - Rakefile
-- VERSION
-- api.yaml
 - 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.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
 - scripts/assemble/Dockerfile
 - scripts/assemble/run.sh
-- scripts/lint.sh
-- scripts/lint/Dockerfile
-- scripts/lint/run.sh
 - scripts/publish.sh
 - scripts/publish/Dockerfile
 - scripts/publish/run.sh
-- scripts/run-tests-e2e.sh
-- scripts/run-tests.sh
-- scripts/test-e2e/Dockerfile
-- scripts/test-e2e/run.sh
+- scripts/run-test-e2e.sh
+- scripts/run-test-local.sh
 - scripts/test/Dockerfile
 - scripts/test/run.sh
 - spec/api_client_spec.rb
 - spec/configuration_spec.rb
 - spec/spec_helper.rb
-- spec/test_aliases_api_spec.rb
+- spec/test_api_spec.rb
+- vgs_api_client-0.0.1.dev202204181658.gem
 - vgs_api_client.gemspec
-homepage: https://github.com/verygoodsecurity/vgs-api-client-ruby
+homepage: https://openapi-generator.tech
 licenses:
-- BSD-3-Clause
-metadata:
-  homepage_uri: https://www.verygoodsecurity.com
-  bug_tracker_uri: https://github.com/verygoodsecurity/vgs-api-client-ruby/issues
-  documentation_uri: https://www.verygoodsecurity.com/docs
-  source_code_uri: https://github.com/verygoodsecurity/vgs-api-client-ruby
+- Unlicense
+metadata: {}
 post_install_message:
 rdoc_options: []
 require_paths:
@@ -122,7 +111,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.6'
+      version: '2.4'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">"
@@ -132,9 +121,9 @@ requirements: []
 rubygems_version: 3.3.7
 signing_key:
 specification_version: 4
-summary: Very Good Security API Client
+summary: A ruby wrapper for the VGS Vault API
 test_files:
 - spec/api_client_spec.rb
 - spec/configuration_spec.rb
 - spec/spec_helper.rb
-- spec/test_aliases_api_spec.rb
+- spec/test_api_spec.rb

data/README.md

@@ -1,39 +0,0 @@
-# vgs-api-client-ruby
-
-[![CircleCI](https://circleci.com/gh/verygoodsecurity/vgs-api-client-ruby.svg?style=svg)](https://github.com/verygoodsecurity/vgs-api-client-ruby)
-
-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](https://github.com/verygoodsecurity/vgs-api-client-ruby/blob/master/DEVELOPMENT.md) instruction.
-
-### Release
-
-Follow [RELEASE](https://github.com/verygoodsecurity/vgs-api-client-ruby/blob/master/RELEASE.md) instruction.
-
-### Documentation
-
-https://www.verygoodsecurity.com/docs/vault/api/
-
-### Tutorial
-
-https://www.verygoodsecurity.com/docs/tokenization/ruby-tutorial
-
-### Artifact
-
-https://rubygems.org/gems/vgs_api_client/
-
-### Support
-
-support@verygoodsecurity.com

data/VERSION

@@ -1 +0,0 @@
-0.0.1.alpha202401251923