Skip to content

[Security Solution] Cypress: Also cleanup proxy handler projects#192213

Merged
dkirchan merged 14 commits intoelastic:mainfrom
jesse-sant:cypress_also_cleanup_proxy_handler
Feb 12, 2025
Merged

[Security Solution] Cypress: Also cleanup proxy handler projects#192213
dkirchan merged 14 commits intoelastic:mainfrom
jesse-sant:cypress_also_cleanup_proxy_handler

Conversation

@jesse-sant
Copy link
Copy Markdown
Contributor

@jesse-sant jesse-sant commented Sep 5, 2024

Summary

Based on a request in this issue. The Cypress cleanup task for serverless testing didn't include a command to cleanup the project tested against when that project was created using the proxy handler. This PR adds a second conditional method in the cleanup task to cleanup projects with the proxy handler when it is in use.

Checklist

  • Cypress tests run with proxy handler
  • Projects created during a cypress run with the proxy handler are automatically cleaned up by the cypress cleanup task

For maintainers

@jesse-sant jesse-sant added release_note:skip Skip the PR/issue when compiling release notes v8.16.0 Team: Sec Eng Productivity AET Security Engineering Productivity team labels Sep 5, 2024
@jesse-sant jesse-sant requested a review from dkirchan September 5, 2024 18:49
@jesse-sant jesse-sant self-assigned this Sep 5, 2024
Copy link
Copy Markdown
Contributor

@maximpn maximpn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -464,6 +464,10 @@ ${JSON.stringify(cypressConfigFile, null, 2)}
if (cloudHandler instanceof CloudHandler) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I'd move a cleanup task to a function for better readability and modularability.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, however I am still learning this code structure, and the next task I am working on is generalizing functionality in the parallel and parallel_serverless scripts out into a common file. I think that PR would be a better place for restructuring something like this call.

@jesse-sant
Copy link
Copy Markdown
Contributor Author

@elasticmachine merge upstream

@kibana-ci
Copy link
Copy Markdown

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @jesse-sant

@banderror banderror marked this pull request as draft November 22, 2024 11:06
@jesse-sant jesse-sant marked this pull request as ready for review December 2, 2024 21:24
@jesse-sant
Copy link
Copy Markdown
Contributor Author

@elasticmachine merge upstream

@elasticmachine
Copy link
Copy Markdown
Contributor

merge conflict between base and head

@dkirchan dkirchan added the backport:skip This PR does not require backporting label Feb 11, 2025
@dkirchan dkirchan enabled auto-merge (squash) February 12, 2025 14:04
@dkirchan dkirchan merged commit 62977e7 into elastic:main Feb 12, 2025
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Jest Tests #19 / SolutionFilter when the owner is a single solution should call onChange with selected solution id when no option selected yet

Metrics [docs]

✅ unchanged

History

cc @jesse-sant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team: Sec Eng Productivity AET Security Engineering Productivity team v8.16.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants