Skip to content

Latest commit

 

History

History
44 lines (34 loc) · 1.94 KB

README.md

File metadata and controls

44 lines (34 loc) · 1.94 KB
Raw

Bulkinout

Reports bulk processing duration for various methods of bulk:

  1. By paging a Cloud Elements resource
  2. By posting to Cloud Elements bulk resource
  3. By paging the vendor resource directly

See bulk directory for the various tests:

  1. ce-get: Performs GET on the specified resource, paging until all results are found and aggregates all results to an array
  2. connector-js: Derived from connector.js, written for MSTR fetchTable function and updated to use node/request-promise rather than browser/JQuery. This process submits a bulk query to Cloud Elements, checks status until finished, then requests the json result and performs a fixJson function to ensure bulk results are always in a json array.
  3. vendorname-vendor-direct-get: Copies of ce-get customized for the vendor. Also depends on a custom version of api.js. TODO: consolidate the differences and abstract the implementation.

Usage

  1. Set environment variables:

Cloud Elements Info

BASE_URL=[cloud elements api base]
USER_SECRET=[cloud elements secret]
ORG_SECRET=[cloud elements secret]

tip set DOCTOR_ACCOUNT=[instead of BASE_URL, USER_SECRET, ORG_SECRET]

Element Info

BULKINOUT_ELEMENT_TOKEN= [cloud elements element token]
BULKINOUT_ELEMENT_KEY= [cloud elements element key]
BULKINOUT_ELEMENT_RESOURCE:[cloud elements element resource name]

Vendor Direct

Requires additional parameters and custom implementation.

# smartrecruiters
BULKINOUT_VENDOR_TOKEN=[can obtain via element builder prehook]
BULKINOUT_VENDOR_RESOURCE=[defaults to ELEMENT_RESOURCE]
BULKINOUT_VENDOR_BASE_URL=[obtain from vendor docs]
  1. $ npm start

Each test will output record count status to the console and append final results to results.csv located in the root directory.