Create a reproducible E2E manual testing env for running LS in FIPS mode #17010
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit pushes configuration files to `qa/fips` for a portable environment for running logstash configured for end to end testing of logstash configured to run with BC providers. Currently it tests the beats input and the elasticsearch output which should be representative of plugins which will require FIPS crypto. The intention here is to have a common shared environment for everyone on the project to be able to reference as we propose changes.
💔 Build Failed
Failed CI StepsHistory |
|
donoghuc
commented
Feb 4, 2025
|
|
||
| ENV JAVA_SECURITY_PROPERTIES=/etc/java/security/java.security | ||
| ENV JAVA_OPTS="\ | ||
| -Dio.netty.ssl.provider=JDK \ |
There was a problem hiding this comment.
We probably want this so that it does not try to use openssl as default https://netty.io/4.1/api/io/netty/handler/ssl/SslContext.html#defaultClientProvider--
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release notes
[rn:skip]
What does this PR do?
This commit pushes configuration files to
qa/fipsfor a portable environment for running logstash configured for end to end testing of logstash configured to run with BC providers. Currently it tests the beats input and the elasticsearch output which should be representative of plugins which will require FIPS crypto.The intention here is to have a common shared environment for everyone on the project to be able to reference as we propose changes.
Why is it important/What is the impact to the user?
This is just for internal use for now.
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files (and/or docker env variables)- [ ] I have added tests that prove my fix is effective or that my feature worksAuthor's Checklist
How to test this PR locally
Check the README.md file i published!