Skip to content
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

Add fips_enabled config parameter to log data streams #302

Merged
merged 2 commits into from
Oct 8, 2020
Merged

Add fips_enabled config parameter to log data streams #302

merged 2 commits into from
Oct 8, 2020

Conversation

kaiyan-sheng
Copy link
Contributor

@kaiyan-sheng kaiyan-sheng commented Oct 7, 2020

What does this PR do?

This PR is to add fips_enabled config option into the integration as a part of elastic/beats#21286.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all datasets collect metrics or logs.

Screenshots

Screen Shot 2020-10-07 at 1 00 58 PM

@elasticmachine
Copy link

Pinging @elastic/integrations-platforms (Team:Platforms)

@elasticmachine
Copy link

elasticmachine commented Oct 7, 2020

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: [Branch indexing]

  • Start Time: 2020-10-08T13:11:48.836+0000

  • Duration: 10 min 36 sec

Copy link
Contributor

@mtojek mtojek left a comment

Choose a reason for hiding this comment

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

LGTM!

@kaiyan-sheng kaiyan-sheng merged commit 6ab8269 into elastic:master Oct 8, 2020
@kaiyan-sheng kaiyan-sheng deleted the add_fips_enabled branch October 8, 2020 14:03
eyalkraft pushed a commit to build-security/integrations that referenced this pull request Mar 30, 2022
* Add fips_enabled config parameter to log data streams

* Fix bool type
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.

3 participants