Fix e2e test cleanup: log drains deletion and reliability improvements #193
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.
Context
The e2e test suite creates applications with log drains attached during log command tests. After tests complete, the cleanup phase tears down all created resources (applications, addons, organisations, etc.).
Problem
Log drains created during tests were not being cleaned up because the API does not automatically delete them when the application is deleted. This left orphaned log drains behind after each test run.
Additionally, cleanup used
Promise.allwhich would abort early on the first rejection, meaning subsequent resources were never cleaned up. Test timeouts were also too low for slow API responses, causing spurious failures.The access log test asserted
typeas"http"but the API actually returns"https".Solution
Promise.alltoPromise.allSettledin all cleanup functions so that a single failure doesn't prevent other resources from being cleaned up.