Merge pull request #30 from antonku/chore/upgrade-aws-sdk

chore: aws-sdk v2 -> v3 migration

.travis.yml

@@ -1,7 +1,7 @@
 language: node_js
 node_js:
-  - 8
-  - 12
+  - 14
+  - 16
 env:
   - VAULT_VERSION=0.7.2
   - VAULT_VERSION=0.8.2
@@ -16,4 +16,4 @@ install:
   - npm install
   - npm install config
 script:
-  - npm test
+  - npm test

CHANGELOG.md

@@ -0,0 +1,53 @@
+# 1.0.0. Release notes (2023-08-02)
+
+- `aws-sdk` is no longer a peer dependency
+- [BREAKING] From now on the minimum supported version of Node.js is 14.0.0.
+- [BREAKING] Changes in IAM configuration. If you explicitly passed aws-sdk@2 credentials to `VaultClient.boot` like below:
+```js
+    const vaultClient = VaultClient.boot('main', {
+    api: {url: 'https://vault.example.com:8200/'},
+    auth: {
+        type: 'iam',
+        mount: 'example',
+        config: {
+            iam_server_id_header_value: 'example',
+            role: 'example',
+            credentials: AWS.CredentialProviderChain.defaultProviders  // <-- this line
+        }
+    },
+});
+```
+This will no longer work. You need to either:
+- Do not pass the credentials at all and rely on the credentials auto-discovery
+```js    
+const vaultClient = VaultClient.boot('main', {
+    api: {url: 'https://vault.example.com:8200/'},
+    auth: {
+        type: 'iam',
+        mount: 'example',
+        config: {
+            iam_server_id_header_value: 'example',
+            role: 'example',
+        }
+    },
+});
+```
+[OR]
+- Pass the credentials explicitly in the following format
+```js
+const vaultClient = VaultClient.boot('main', {
+    api: {url: 'https://vault.example.com:8200/'},
+    auth: {
+        type: 'iam',
+        mount: 'example',
+        config: {
+            iam_server_id_header_value: 'example',
+            role: 'example',
+            credentials: {
+                accessKeyId: 'AWS_ACCESS_KEY',
+                secretAccessKey: 'AWS_SECRET_KEY',
+            }
+        }
+    },
+});
+```