-
Notifications
You must be signed in to change notification settings - Fork 24.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
Fix Azure tests in FIPS mode again #111611
Fix Azure tests in FIPS mode again #111611
Conversation
Closes elastic#111345 Closes elastic#111607 Closes elastic#111608
Pinging @elastic/es-distributed (Team:Distributed) |
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
Btw, you can tag a PR with :Security/FIPS
to get FIPS CI running for it when necessary. Not really useful for this one since it is disabling them.
if (BuildParams.inFipsJvm) { | ||
// Cannot override the trust store in FIPS mode, and these tasks require a HTTPS fixture | ||
tasks.named("managedIdentityYamlRestTest").configure { enabled = false } | ||
tasks.named("workloadIdentityYamlRestTest").configure { enabled = false } | ||
} |
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.
Since we disable these tests globally, I think we should remove the ESTestCase.inFipsJvm()
in RepositoryAzureClientYamlTestSuiteIT
and AzureSnapshotRepoTestKitIT
? IIUC, we will always use HTTPS fixture when fixture is in use? If so, might also make sense to merge USE_FIXTURE
and USE_HTTPS_FIXTURE
into one. Can be a follow-up if you prefer.
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.
We run the regular yamlRestTest
variants of RepositoryAzureClientYamlTestSuiteIT
and AzureSnapshotRepoTestKitIT
in FIPS mode too, and we want to use the HTTP fixture in those cases.
Pinging @elastic/es-security (Team:Security) |
TIL, thanks. I was wondering why we didn't have a label for triggering these CI jobs. |
Closes elastic#111345 Closes elastic#111607 Closes elastic#111608
Closes #111345
Closes #111607
Closes #111608