-
Notifications
You must be signed in to change notification settings - Fork 198
Temporarily disable FIPS integration tests #10006
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
|
This pull request does not have a backport label. Could you fix it @ycombinator? 🙏
|
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
|
Hmmm, looks like the FIPS integration testing pipeline is still being triggered. 🤔 |
Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
|
|
Closing this PR in favor of #10007, as that PR keeps running the FIPS integration tests, just against the Production CFT region instead of the Staging GovCloud region (temporarily). |





What does this PR do?
This PR temporarily disables the FIPS integration testing Buildkite pipeline.
Why is it important?
The FIPS integration tests pipeline is currently failing because the step where it provisions deployments in GovCloud Staging is consistently failing. So we are disabling the FIPS integration tests pipeline until the underlying issues in the GovCloud Staging environment are resolved.