Temporarily have FIPS integration tests spin up deployments in Production CFT environment #10007
Conversation
This file contains hidden or 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
ycombinator
added
Team:Elastic-Agent-Control-Plane
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
v1v
previously approved these changes
Sep 17, 2025
Comment on lines
15
to
19
| - vault_ec_key_staging_frh_gov: &vault_ec_key_staging_frh_gov | ||
| # - vault_ec_key_staging_frh_gov: &vault_ec_key_staging_frh_gov | ||
| # elastic/vault-secrets#v0.1.0: | ||
| # path: "kv/ci-shared/platform-ingest/platform-ingest-ec-staging-gov" | ||
| # field: "apiKey" | ||
| # env_var: "EC_API_KEY" |
There was a problem hiding this comment.
I think you can keep this YAML anchor, without commenting out, then you just use the other one
There was a problem hiding this comment.
Yeah, I thought about that but wanted to deliberately comment it out so we know it's being (temporarily) replaced by the other one. I'll add a comment inline explaining that.
There was a problem hiding this comment.
Added explanation in 2c6b4ad.
ebeahan
previously approved these changes
Sep 17, 2025
v1v
previously approved these changes
Sep 17, 2025
|
FIPS integration testing steps ran successfully in the last CI run so removing ae0e89d from this PR now. This will let us easily revert the changes in this PR once the Staging GovCloud issues are fixed. To be clear, we need the change in ae0e89d for the long term, so that's been added in a separate PR: #10008 |
This reverts commit ae0e89d.
mergify bot
pushed a commit
that referenced
this pull request
Sep 17, 2025
…tion CFT environment (#10007) * Have FIPS integration tests spin up deployments in Production CFT environment * Add explanatory comment * Run extended tests if FIPS integration tests pipeline changes * Revert "Run extended tests if FIPS integration tests pipeline changes" This reverts commit ae0e89d. (cherry picked from commit c76bfe2)
mergify bot
pushed a commit
that referenced
this pull request
Sep 17, 2025
…tion CFT environment (#10007) * Have FIPS integration tests spin up deployments in Production CFT environment * Add explanatory comment * Run extended tests if FIPS integration tests pipeline changes * Revert "Run extended tests if FIPS integration tests pipeline changes" This reverts commit ae0e89d. (cherry picked from commit c76bfe2)
ycombinator
added a commit
that referenced
this pull request
Sep 18, 2025
…tion CFT environment (#10007) (#10011) * Have FIPS integration tests spin up deployments in Production CFT environment * Add explanatory comment * Run extended tests if FIPS integration tests pipeline changes * Revert "Run extended tests if FIPS integration tests pipeline changes" This reverts commit ae0e89d. (cherry picked from commit c76bfe2) Co-authored-by: Shaunak Kashyap <ycombinator@gmail.com>
|
💛 Build succeeded, but was flaky
Failed CI StepsHistory
cc @ycombinator |
cmacknz
pushed a commit
that referenced
this pull request
Sep 18, 2025
…tion CFT environment (#10007) * Have FIPS integration tests spin up deployments in Production CFT environment * Add explanatory comment * Run extended tests if FIPS integration tests pipeline changes * Revert "Run extended tests if FIPS integration tests pipeline changes" This reverts commit ae0e89d.
intxgo
pushed a commit
to intxgo/elastic-agent
that referenced
this pull request
Sep 24, 2025
…tion CFT environment (elastic#10007) * Have FIPS integration tests spin up deployments in Production CFT environment * Add explanatory comment * Run extended tests if FIPS integration tests pipeline changes * Revert "Run extended tests if FIPS integration tests pipeline changes" This reverts commit ae0e89d.
This was referenced Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What does this PR do?
This PR temporarily creates ECH deployments for the FIPS integration testing Buildkite pipeline in the Production CFT ESS environment (as opposed to the Staging GovCloud ESS environment).
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.