[osquery] Setup E2E against Serverless ES, Kibana, Fleet server standalone and Elastic agents in Docker#165415
Conversation
df547a1 to
8a2243e
Compare
# Conflicts: # x-pack/plugins/security_solution/scripts/endpoint/common/stack_services.ts
# Conflicts: # x-pack/plugins/security_solution/scripts/endpoint/common/fleet_services.ts # x-pack/plugins/security_solution/scripts/endpoint/common/stack_services.ts
This reverts commit be6c000.
paul-tavares
left a comment
There was a problem hiding this comment.
Thanks for working on this. 👍
# Conflicts: # x-pack/plugins/fleet/server/config.ts
MadameSheema
left a comment
There was a problem hiding this comment.
Please socialize before merging that docker is going to be needed as well for executing Cypress ESS in the local machine. Thanks.
MadameSheema
left a comment
There was a problem hiding this comment.
Please socialize before merging that docker is going to be needed as well for executing Cypress ESS in the local machine. Thanks.
What this PR Does
Note: this isn't intended to cause any changes to how SAET tests run today. Breaking changesYou'll need docker installed locally to run tests with these changes. @patrykkopycinski may be able to change this limitations. Changes to kbn-dev-utils & kbn-crypto
Changes to kbn-es
Changes to x-pack/plugins/fleet
Follow up ideas:
|
|
|
||
| # Extract the PEM-formatted PKCS #1 private key for Elasticsearch | ||
| openssl pkcs12 -in elasticsearch.p12 -nocerts -passin pass:"storepass" -passout pass:"keypass" | openssl rsa -passin pass:keypass -out elasticsearch.key | ||
| openssl pkcs12 -in elasticsearch.p12 -nocerts -passin pass:"storepass" -passout pass:"keypass" | openssl rsa -passin pass:keypass -out elasticsearch.key -traditional |
There was a problem hiding this comment.
I could not find documentation on the -traditional option. What does it do?
There was a problem hiding this comment.
Update: found it..."When writing a private key, use the traditional PKCS#1 format instead of the PKCS#8 format". All set.
|
@oatkiller Thanks a lot for writing up this summary: #165415 (comment). Could you please elaborate on this:
What SAET Cypress serverless tests will be affected by this PR, and what does it mean "will not run"? |
I believe this is just stating that SAET tests are currently not going to run against the serverless ES in docker. Not that SAET tests are being broken by this PR. The follow up PRs could adjust the SAET tests to also run in this manner. cc @oatkiller |
…-ref HEAD~1..HEAD --fix'
💔 Build FailedFailed CI Steps
Test Failures
Metrics [docs]Public APIs missing comments
Unknown metric groupsAPI count
History
To update your PR or re-run it, just comment with: |
Summary
Let's automate E2E against Serverless
Changelog:
host.docker.internal,es01openssl@3ca_trusted_fingerprintin fleet preconfig