sailor-nodejs: 2.6.24 (#9)

* Update sailor version to 2.6.24

* npm audit-level= high --> critical

Author: stas-fomenko

.circleci/config.yml

@@ -9,7 +9,7 @@ jobs:
           key: dependency-cache-{{ checksum "package.json" }}
       - run:
           name: Audit Dependencies
-          command: npm audit --audit-level=high
+          command: npm audit --audit-level=critical
       - run:
           name: Installing Dependencies
           command: npm install

CHANGELOG.md

@@ -1,3 +1,7 @@
+## 2.0.4 (February 12, 2021)
+
+* Update sailor version to 2.6.24
+
 ## 2.0.3 (November 18, 2020)
 
 * Fix fields dependencies from sobject field in component.json, [issue 5](https://github.com/elasticio/salesforce-component-v2/issues/5)

README.md

@@ -38,7 +38,6 @@ The component uses Salesforce - API Version 46.0 by defaults but can be overwrit
 ### Environment variables
 Name|Mandatory|Description|Values|
 |----|---------|-----------|------|
-|LOG_LEVEL| false | Controls logger level | `trace`, `debug`, `info`, `warn`, `error` |
 |SALESFORCE_API_VERSION| false | Determines API version of Salesforce to use | Default: `46.0` |
 |REFRESH_TOKEN_RETRIES| false | Determines how many retries to refresh token should be done before throwing an error | Default: `10` |
 |HASH_LIMIT_TIME| false | Hash expiration time in ms  | Default: `600000` |
@@ -220,9 +219,11 @@ Metadata contains one field whose name, type and mandatoriness are generated acc
 Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.
 
 #### Limitations
-When a binary field (primitive type `base64`, e.g. Documents, Attachments, etc) is selected on **Include linked objects**, an error will be thrown: 'MALFORMED_QUERY: Binary fields cannot be selected in join queries. Instead of querying objects with binary fields as linked objects (such as children Attachments), try querying them directly.' There is also a limit to the number of linked objects that you can query at once - beyond two or three, depending on the number of fields in the linked objects, Salesforce could potentially return a Status Code 431 or 414 error, meaning the query is too long. Finally, due to a bug with multiselect dropdowns, it is recommended to deselect all of the elements in this field before you change your selection in the *Object* dropdown list.
+1. When a binary field (primitive type `base64`, e.g. Documents, Attachments, etc) is selected on **Include linked objects**, an error will be thrown: `MALFORMED_QUERY: Binary fields cannot be selected in join queries. Instead of querying objects with binary fields as linked objects (such as children Attachments), try querying them directly.` 
+There is also a limit to the number of linked objects that you can query at once - beyond two or three, depending on the number of fields in the linked objects, Salesforce could potentially return a Status Code 431 or 414 error, meaning the query is too long. Finally, due to a bug with multiselect dropdowns, it is recommended to deselect all of the elements in this field before you change your selection in the *Object* dropdown list.
 
-When **Pass binary data to the next component (if found object has it)** is checked and this action is used with Local Agent, an error will be thrown: 'getaddrinfo ENOTFOUND steward-service.platform.svc.cluster.local steward-service.platform.svc.cluster.local:8200'
+2. Not supported object lookup when selected field value is `null`  
+3. When **Pass binary data to the next component (if found object has it)** is checked and this action is used with Local Agent, an error will be thrown: 'getaddrinfo ENOTFOUND steward-service.platform.svc.cluster.local steward-service.platform.svc.cluster.local:8200'
 
 #### Note
 Action has caching mechanism. By default action stores last 10 request-response pairs for 10 min duration.
@@ -312,4 +313,4 @@ Output metadata is the same as input metadata, so you may expect all fields that
 When **Utilize data attachment from previous step (for objects with a binary field)** is checked and this action is used with Local Agent error would be thrown: 'getaddrinfo ENOTFOUND steward-service.platform.svc.cluster.local steward-service.platform.svc.cluster.local:8200'
 
 ## Known limitations
-Attachments mechanism does not work with [Local Agent Installation](https://support.elastic.io/support/solutions/articles/14000076461-announcing-the-local-agent-)
+Attachments mechanism does not work with [Local Agent Installation](https://docs.elastic.io/getting-started/local-agent.html)

component.json

@@ -326,7 +326,7 @@
         },
         "passBinaryData": {
           "viewClass": "CheckBoxView",
-          "label": "Pass binary data to the next component (if found object has it)",
+          "label": "Pass binary data to the next step (if found object has it)",
           "order": 2
         },
         "enableCacheUsage": {

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "salesforce-component-v2",
-  "version": "2.0.3",
+  "version": "2.0.4",
   "description": "elastic.io component that connects to Salesforce API (node.js) v2",
   "main": "index.js",
   "scripts": {
@@ -24,13 +24,13 @@
   },
   "homepage": "https://github.com/elasticio/salesforce-component#readme",
   "engines": {
-    "node": "12.18.2"
+    "node": ">=12.18.2"
   },
   "dependencies": {
     "axios": "0.20.0",
     "elasticio-node": "0.0.9",
     "elasticio-rest-node": "1.2.6",
-    "elasticio-sailor-nodejs": "2.6.18",
+    "elasticio-sailor-nodejs": "2.6.24",
     "jsforce": "1.10.0",
     "mime-types": "2.1.27",
     "request": "2.88.2",