-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[elastic/beats] [HttpJson] - Improves request chaining with new 'while' step & client creation per step #32222
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some questions to review, mostly around docs/language. Please have a look.
I see that some of the issues with the docs were already present, I've created #32321 to remember to fix them.
Co-authored-by: Adrian Serrano <[email protected]>
Co-authored-by: Adrian Serrano <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a final adjustment to the docs
[float] | ||
==== `chain[].while.replace` | ||
|
||
Please refer `chain[].step.replace`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR still adds a few "Please refer X" expressions. My understanding is that those are not correct, please correct me if I'm wrong.
I lean towards using "See X" instead of "Please refer to X for more information" as a replacement.
Also, this one uses a `literal` instead of a <<link>>, can it be turned into a link?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adriansr updated the docs as per the suggestions. Please review once.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question. Other than that LGTM
…e' step & client creation per step (#32222) * initial commit * While block introduced in chain config, per step creation of httpclient added as an improvement. * removed debug code * added auth inheriting from parent * updated docs * made linter recommended fixes * made recommended changes as per PR suggetions * added tests * fixed errors for linting checks * eliminated specifying nill values * made till , a mandatory parameter for whileconfig * Update x-pack/filebeat/input/httpjson/policy.go Co-authored-by: Adrian Serrano <[email protected]> * Update x-pack/filebeat/docs/inputs/input-httpjson.asciidoc Co-authored-by: Adrian Serrano <[email protected]> * updated docs , made PR fixes * updated the docs as per suggetions Co-authored-by: Adrian Serrano <[email protected]>
Type of change
- Enhancement
What does this PR do?
Introduced new request chain step 'while' to tackle scenarios as reported in this ticket : [Filebeat][httpjson input] Add status check API calls. #29959
Added support for creation of of new http client per step in the request chain , thereby enabling individual steps to
take advantage of unique auth's per step if required and access to all request parameters. This also helps lay the foundations
for solving the the issue : [Filebeat][Inputs][HTTP JSON] Multi-Step/API Requests #31117.
[Note] : if an auth per step is not defined , the steps shall inherit any auth that is used in the root request call.
Added an improvement which now removes the requirement for request.retry.wait_max field to be specified everywhere
even when it is not required. Now you can simply specify request.retry.wait_min for the retry config and the wait will occur.
You can still specify both fields ..when they have different values. Previously only specifying request.retry.wait_min caused
the wait not not occur.
Checklist
- [ ] I have made corresponding change to the default configuration filesinput-httpjson.asciidoc
.Related issues