Skip to content

[9.4](backport #50005) Temporarily have FIPS integration tests spin up deployments in Production CFT environment#50012

Merged
ycombinator merged 1 commit into9.4from
mergify/bp/9.4/pr-50005
Apr 8, 2026
Merged

[9.4](backport #50005) Temporarily have FIPS integration tests spin up deployments in Production CFT environment#50012
ycombinator merged 1 commit into9.4from
mergify/bp/9.4/pr-50005

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Apr 8, 2026

Proposed commit message

This PR temporarily creates ECH deployments for the FIPS integration testing Buildkite pipelines (x-pack/filebeat and x-pack/metricbeat) in the Production CFT ESS environment (as opposed to the Staging GovCloud ESS environment).

The FIPS ECH integration tests are currently failing because the step where deployments are provisioned in GovCloud Staging is consistently failing due to an ongoing incident in that environment. This change should be reverted once FRH Staging is healthy again.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
  • I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

None. CI-only change.


This is an automatic backport of pull request #50005 done by Mergify.

FRH Staging is currently unable to provision deployments, causing the
x-pack/{filebeat,metricbeat} FIPS ECH integration tests to fail. This
temporarily points those pipelines at the Production CFT environment
until the incident is resolved. Revert once FRH Staging is healthy.

(cherry picked from commit 08e091f)
@mergify mergify bot added the backport label Apr 8, 2026
@mergify mergify bot requested a review from a team as a code owner April 8, 2026 18:14
@mergify mergify bot added the backport label Apr 8, 2026
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 8, 2026
@github-actions github-actions bot added release-note:skip The PR should be ignored when processing the changelog Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Apr 8, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 8, 2026

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Apr 8, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@ycombinator ycombinator merged commit 84140f0 into 9.4 Apr 8, 2026
53 checks passed
@ycombinator ycombinator deleted the mergify/bp/9.4/pr-50005 branch April 8, 2026 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport release-note:skip The PR should be ignored when processing the changelog Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants