Cherry-pick #18953 to 7.x: Add Okta module documentation, config cleanup, _id field #19051
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #18953 to 7.x branch. Original message:
What does this PR do?
This add documentation for the Okta module. It contains descriptions of the
configuration options and general information about the module.
I fixed an issue with the module where it was not setting the
_id
field for Elasticsearch events.I also did some cleanup to the pipeline.js (indentation, semi-colons, strict equality checks).
The module's manifest was updated to not duplicate httpjson's default values.
The module was accepting configuration as JSON strings for some parameters (
http_headers
,http_request_body
,pagination
,rate_limit
,ssl
) which is inconsistent with how other parts of Beats are configured so I removed this. Now these options expect regular YAML objects for values. None of these options are required to use the module so the impact to users should be minimal.Why is it important?
Documentation is required for users to know how to use the module.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Logs
I ran the module against the Okta API to test. You'll note that the
@metadata._id
field is now set which libbeat will use when writing the data to Elasticsearch.