fix(core): share request config across all requests (#928)

* fix added by bumping core to 0.3.5
* this will allow users to configure all requests, which fixes a bug that prevented use of the SDK behind a corporate proxy
* documentation added for this use case in the readme

(cherry picked from commit 7fd5577)

Author: dpopp07

README.md

@@ -24,6 +24,7 @@ Node.js client library to use the Watson APIs.
   * [Sending request headers](#sending-request-headers)
   * [Parsing HTTP response](#parsing-http-response)
   * [Data collection opt-out](#data-collection-opt-out)
+  * [Using the SDK behind a corporate proxy](#using-the-sdk-behind-a-corporate-proxy)
   * [Documentation](#documentation)
   * [Questions](#questions)
   * [IBM Watson services](#ibm-watson-services)
@@ -269,18 +270,6 @@ discovery.listEnvironments((err, res) => {
 });
 ```
 
-### Setting the service URL
-
-You can set the service URL by calling the setServiceUrl() method.
-
-```javascript
-const discovery = new DiscoveryV1({
-  version: '<version-date>'
-});
-
-discovery.setServiceUrl('https://gateway-wdc.watsonplatform.net/discovery/api');
-```
-
 ### Sending request headers
 
 Custom headers can be passed with any request. Each method has an optional parameter `headers` which can be used to pass in these custom headers, which can override headers that we use as parameters.
@@ -355,6 +344,24 @@ var myInstance = new watson.WhateverServiceV1({
 });
 ```
 
+### Using the SDK behind a corporate proxy
+
+To use the SDK (which makes HTTPS requests) behind an HTTP proxy, a special tunneling agent must be used. Use the package [`tunnel`](https://github.com/koichik/node-tunnel/) for this. Configure this agent with your proxy information, and pass it in as the HTTPS agent in the service constructor. Additionally, you must set `proxy` to `false` in the service constructor. See this example configuration:
+```js
+const tunnel = require('tunnel');
+const AssistantV1 = require('ibm-watson/assistant/v1');
+
+const assistant = new AssistantV1({
+  iam_apikey: 'fakekey1234',
+  version: '2019-02-28',
+  httpsAgent: tunnel.httpsOverHttp({
+    host: 'some.host.org',
+    port: 1234,
+  }),
+  proxy: false,
+});
+```
+
 ### Configuring the HTTP client
 
 The HTTP client can be configured to disable SSL verification. Note that this has serious security implications - only do this if you really mean to! ⚠️

package-lock.json

@@ -86,7 +86,7 @@
     "axios": "^0.18.0",
     "dotenv": "^6.2.0",
     "extend": "~3.0.2",
-    "ibm-cloud-sdk-core": "^0.3.4",
+    "ibm-cloud-sdk-core": "^0.3.5",
     "isstream": "~0.1.2",
     "object.pick": "~1.3.0",
     "snyk": "^1.192.4",