sqewer 8.0.1 → 8.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: db608a0341020c8df0186ebc598164f5efef1c75051b4661aabb6e8c7e5c4406
-  data.tar.gz: 3823ade5a67c8e66844eed3e267f5d5c4f0b6f3626c53c645d22ebb57b25ed12
+  metadata.gz: c3bde02330a40856f767370e8098ec7e11216c1434977b8072cdd78af410d132
+  data.tar.gz: 79a8fae95732af97fee2faa101abe058015e542fafe00c6f193298a8d2a9db29
 SHA512:
-  metadata.gz: 2c549285412294f21ec5a8af1d5614e949941996c687b91478c5a1ed4553995e888aa56443dde5c6eace899b24d44d5a02e21dfb61d391408e126c01b001e3dd
-  data.tar.gz: 49b1d928b6786d38911db7803498a42fd4860c8c7723ec09a477b464103eded17a752d3f900c01f20af5cd0d6d79360d260d78a7636a0a8c1f7e6e322554e209
+  metadata.gz: d0ee92f90995e1ad4fc439da92550fb6e9a9a294941b444a41b761e5589d82fb4cc4e5d7252359bc5b22f5675d6dcfb7f4dfb1fcf81e7376e3939f6a7e6cccd2
+  data.tar.gz: f95b7659f1fa00b51a0f4882515b5f0c6d655148849de83b9da4bf104814ccfe0a192cf617c1a56a2c154c8f79331ee5e6acb6979f7d795fc68ee4fc3401f831

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+### 8.0.2
+- Add `Aws::SQS::Errors::AccessDenied` to the list of errors that Sqewer must release the singleton SQS client
+
 ### 8.0.1
 - Release the singleton SQS client when AWS raises credentials error to be able to use a new credential next time
 

data/lib/sqewer/connection.rb

@@ -13,6 +13,11 @@ class Sqewer::Connection
 
   NotOurFaultAwsError = Class.new(Sqewer::Error)
 
+  SQS_ERRORS_TO_RELEASE_CLIENT = [
+    Aws::Errors::MissingCredentialsError,
+    Aws::SQS::Errors::AccessDenied,
+  ]
+
   # A wrapper for most important properties of the received message
   class Message < Struct.new(:receipt_handle, :body, :attributes)
     def inspect
@@ -76,7 +81,7 @@ class Sqewer::Connection
       )
       response.messages.map {|message| Message.new(message.receipt_handle, message.body, message.attributes) }
     end
-  rescue Aws::Errors::MissingCredentialsError
+  rescue *SQS_ERRORS_TO_RELEASE_CLIENT
     # We noticed cases where errors related to AWS credentials started to happen suddenly.
     # We don't know the root cause yet, but what we can do is release the
     # singleton @client instance because it contains a cache of credentials that in most
@@ -235,7 +240,7 @@ class Sqewer::Connection
         raise NotOurFaultAwsError
       end
     end
-  rescue Aws::Errors::MissingCredentialsError
+  rescue *SQS_ERRORS_TO_RELEASE_CLIENT
     # We noticed cases where errors related to AWS credentials started to happen suddenly.
     # We don't know the root cause yet, but what we can do is release the
     # singleton @client instance because it contains a cache of credentials that in most

data/lib/sqewer/version.rb

@@ -1,3 +1,3 @@
 module Sqewer
-  VERSION = '8.0.1'
+  VERSION = '8.0.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sqewer
 version: !ruby/object:Gem::Version
-  version: 8.0.1
+  version: 8.0.2
 platform: ruby
 authors:
 - Julik Tarkhanov
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-07-12 00:00:00.000000000 Z
+date: 2021-07-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-sqs