Skip to content

feat(SplunkLogger): Add requestOptions parameter - #16

Merged
bparmar-splunk merged 2 commits into
splunk:developfrom
elliotttf:requestOptions
Sep 30, 2022
Merged

bparmar-splunk merged 2 commits into
splunk:developfrom
elliotttf:requestOptions

Conversation

@elliotttf

@elliotttf elliotttf commented May 5, 2017

Copy link
Copy Markdown

This will allow requestOptions to be passed into the constructor rather than requiring modifications after instantiation. This is particularly useful for assigning multiple options at once, e.g.

const logger = new SplunkLogger(config, {
  agent: new https.Agent(),
  strictSSL: true,
  timeout: 150,
});

@elliotttf
elliotttf changed the base branch from master to develop May 5, 2017 22:05

@chasingmaxwell chasingmaxwell left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@shakeelmohamed

Copy link
Copy Markdown
Contributor

We need to support non-es6 versions of Node. That's the only thing blocking me from merging this - however I can't promise a release anytime soon due to tight engineering resources

@elliotttf
elliotttf force-pushed the requestOptions branch 2 times, most recently from fdec21e to dce4cb2 Compare May 16, 2017 21:12
@elliotttf

Copy link
Copy Markdown
Author

@shakeelmohamed I've re-rolled the commit to not use ES6 features. Let me know if you want me to change anything else.

@shakeelmohamed

Copy link
Copy Markdown
Contributor

Thanks @elliotttf. I updated the jshint config, if you merge/rebase from the develop branch you'll see a couple indent issues to fix.

How urgently do you need a release with this change?

This will allow `requestOptions` to be passed into the constructor
rather than requiring modifications after instantiation. This is
particularly useful for assigning multiple options at once, e.g.

```javascript
const logger = new SplunkLogger(config, {
  agent: new https.Agent(),
  strictSSL: true,
  timeout: 150,
});
```
@elliotttf

Copy link
Copy Markdown
Author

@shakeelmohamed fixed!

It's not urgent but definitely a nice to have. Specifically I'm interested in this so that I have finer grain control over the socket pool that my application uses to communicate with splunk's servers.

It's still possible to do that without this change, just not as convenient 😄

@ABastionOfSanity

Copy link
Copy Markdown

+1

@shakeelmohamed

Copy link
Copy Markdown
Contributor

@elliotttf We've dropped support for pre-4.0 version of Node so we'd be happy to take this PR now! Can you merge the latest develop into your branch so CI runs?

@vinnieking06

Copy link
Copy Markdown

Any update on when this might get merged? Our team is patching the package locally for the time being. Thanks!

@vinnieking06

Copy link
Copy Markdown

@shakeelmohamed or any other maintainer, looks like this one is ready to go when you have a moment to review. Thank you!

@ncanumalla-splunk

ncanumalla-splunk commented Jan 10, 2022

Copy link
Copy Markdown

Hi all, Shakeel is no longer one of the maintainers of this project.
@ashah-splunk Can we please plan to review this PR as one of the next items? Thanks.

@vinnieking06

Copy link
Copy Markdown

Hey splunk team (@ncanumalla-splunk, @ashah-splunk ), any update on when this might get merged? My team appreciates it!

@bparmar-splunk
bparmar-splunk merged commit 80519c0 into splunk:develop Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants