Releases: evervault/evervault-ruby
v3.0.1
v3.0.0
Major Changes
-
f4d3d01: Simplifying errors thrown by the SDK.
Previously we exposed many different error types for users to handle, but in most cases these errors were not something that could be caught and handled, but were rather indicative of a larger configuration issue. This change simplifies the errors thrown by returning an EvervaultError with accompanying error message by default, unless they are a transient error which can be handled programmatically, in which case a specific error is returned.
-
dd84f66: We have dropped support for Ruby 2.6 and 2.7 as they are now both in end of life status.
See more: https://www.ruby-lang.org/en/downloads/branches -
b2188aa: Migrated Function run requests to new API.
We have released a new API for Function run requests which is more robust, more extensible, and which provides more useful error messages when Function runs fail. In addition, we have removed async Function run requests and specifying the version of the Function to run. For more details check out https://docs.evervault.com/sdks/ruby#run()
Minor Changes
-
b7f5c1a: The
encrypt
function has been enhanced to accept an optional Data Role.This role, once specified, is associated with the data upon encryption. Data Roles can be created in the Evervault Dashboard (Data Roles section) and provide a mechanism for setting clear rules that dictate how and when data, tagged with that role, can be decrypted. For more details check out https://docs.evervault.com/sdks/ruby#encrypt()
Evervault.encrypt("hello world!", "allow-all");
Patch Changes
- 7d91003: Add Faraday as a gem dependency
v2.1.0
What's Changed
Creating Client Side Decrypt Tokens
Evervault.create_client_side_decrypt_token
is used to generate a time-bound token that can be used by front-end applications to decrypt Evervault encrypted data.
time_now = Time.now
time_in_five_minutes = time_now + 300
Evervault.create_client_side_decrypt_token(encrypted_data, time_in_five_minutes)
Full Changelog: v2.0.0...v2.1.0
v2.0.0
This new version introduces the following changes:
- The App ID is now required along with the API Key when initialising the SDK. This is a breaking change.
require "evervault"
# Initialize the client with your App's ID and App's API key
Evervault.app_id = <YOUR-APP-ID>
Evervault.api_key = <YOUR-API-KEY>
# Encrypt your data
encrypted_data = Evervault.encrypt('Hello World!')
- Data can be decrypted using the new
decrypt()
function.
# Decrypt your data
Evervault.decrypt(encrypted_data)
// "Hello World!"
Full Changelog: v1.3.2...v2.0.0
v1.3.0
What's Changed
- feat(create_run_token): Allow non preapproved payloads for creating r… by @jakekgrog in #18
- Bump version by @jakekgrog in #19
New Contributors
- @jakekgrog made their first contribution in #18
Full Changelog: v1.2.0...v1.3.0
v1.2.0
This version adds the ability to enable Outbound Relay and automatically sync all relays created in the Evervault UI. This can be enabled using the enable_outbound_relay
method.
# Initialize the client with your team's API key
Evervault.api_key = "<YOUR-API-KEY>"
# Encrypt your data
encrypted_data = Evervault.encrypt({ hello: 'World!' })
# Send the decrypted data to a third-party API
Evervault.enable_outbound_relay
uri = URI('https://example.com')
req = Net::HTTP::Post.new(uri.path, 'Content-Type' => 'application/json')
req.body = encrypted_data.to_json
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
res = http.request(req)
Releasing run token creation
Merge pull request #14 from evervault/deirdre/bump-version Bumping version
Releasing run token creation
v1.1.0 Merge pull request #13 from evervault/deirdre/pro-1548-add-createrunt…
Support prime256v1, secp256k1 and outbound interception
v1.0.0 Merge pull request #10 from evervault/deirdre/pro-800-add-outbound-to…