-
Notifications
You must be signed in to change notification settings - Fork 168
[FIPS][Integration Test] Ensure FIPS-capable Agent can connect to FIPS-capable Fleet Server in an ECH FRH environment #8046
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
[FIPS][Integration Test] Ensure FIPS-capable Agent can connect to FIPS-capable Fleet Server in an ECH FRH environment #8046
Conversation
This pull request does not have a backport label. Could you fix it @ycombinator? 🙏
|
1753a7a
to
9f54dfe
Compare
e10e3c1
to
e4a60cb
Compare
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
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.
Reviewed just the CI changes, LGTM
This pull request is now in conflicts. Could you fix it? 🙏
|
e4a60cb
to
c0072c8
Compare
💛 Build succeeded, but was flaky
Failed CI StepsHistory
cc @ycombinator |
|
…S-capable Fleet Server in an ECH FRH environment (#8046) * WIP: scaffolding for test * WIP: Print out env vars * Update comment * Running mage fmt * Fix syntax errors * Update comments * Flesh out test * Reference PR from elastic-agent-libs * Removing comment * Remove comment that is no longer necessary * Export INTEGRATIONS_SERVER_HOST from ESS deployment's terraform output * Set up INTEGRATIONS_SERVER_HOST environment variable * Fixing API errors * Bump elastic-agent-libs (cherry picked from commit 83ece2c)
What does this PR do?
This PR adds an integration test that ensures that a FIPS-capable Elastic Agent running in an ECH FRH (FedRamp High) environment is able to successfully connect to its own local Fleet Server instance (which, by definition should also be FIPS-capable and running in the ECH FRH environment).
Why is it important?
To ensure that FIPS-capable Agent is able to connect to a FIPS-capable Fleet Server in an ECH FRH environment.
Checklist
[ ] 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[ ] I have added an entry in./changelog/fragments
using the changelog tool