-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Skip netty4 yaml test in FIPS mode #66842
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
Conversation
The "Netty loaded" YAML test asserts that the configured transport is "netty4", however when in FIPS mode, the tests enable security and the configured transport is "security4". This change skips the netty4 yaml test when running in FIPS mode. Resolves: elastic#66818
Pinging @elastic/es-security (Team:Security) |
The original plan was to add this to the yml test:
However, that means that the test suite ended up with no tests, which fails the build. |
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.
LGTM
The "Netty loaded" YAML test asserts that the configured transport is "netty4", however when in FIPS mode, the tests enable security and the configured transport is "security4". This change skips the netty4 yaml test when running in FIPS mode. Resolves: elastic#66818 Backport of: elastic#66842
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.
LGTM
The "Netty loaded" YAML test asserts that the configured transport is
"netty4", however when in FIPS mode, the tests enable security and the
configured transport is "security4".
This change skips the netty4 yaml test when running in FIPS mode.
Resolves: #66818