-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Cloud Security] [Agentless] Create GHA Cloud Security workflow sanity tests for Agentless ESS deployments. #192182
Open
seanrathier
wants to merge
21
commits into
elastic:main
Choose a base branch
from
seanrathier:10269-gha-sanity-tests-for-agentless-ess-deployments
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+62
−99
Open
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
4f34dc5
Added Quality Gates test
seanrathier 0c4c24f
Testing
seanrathier 050ffa3
Testing
seanrathier 6186f64
using the agentless-api test for quality-gates and PR tests
seanrathier a373194
reverting the agentless api test config
seanrathier a32f33d
omit loggin in as admin if running in cloud
seanrathier 0614796
Added login as admin for serverless
seanrathier f5b4879
Merge branch 'main' into 10412-agentless-serverless-quality-gate
elasticmachine f71bebd
fixing type error
seanrathier 3b9875c
Initial tests
seanrathier cd0d867
less flakey
seanrathier b575769
removed commented code
seanrathier 66d9a16
fixing merge conflicts
seanrathier 80d7617
removedthe health check
seanrathier e65815f
Fixed an unwanted merge of agentless_snaity
seanrathier 0dd52d1
Fixed an error
seanrathier 9808b3c
Fixed a typo
seanrathier 0d5b3f2
Added a wait for page to load
seanrathier 05c1974
better testing
seanrathier 23ee4e5
removing commented code
seanrathier 71a47a5
adding tag
seanrathier File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
less flakey
- Loading branch information
commit cd0d867510e161a7f32f55c8dc8ec8ae28547cb2
There are no files selected for viewing
This file contains 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
This file contains 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
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.
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.
I'm not sure if testing agent health through the UI is the most suitable approach for our case. The Fleet component isn't under our responsibility, and although you're using test objects for some parts, you're relying on CSS selectors and retrieving visible text for the verification steps, which is more critical, there's a risk that if the Fleet team changes something related to the UI, it could break our tests.
If we still want to pinpoint where our tests are failing—whether the issue is on the UI side or due to the agent's health—it might be better to use a Fleet API call to verify if the required agent is healthy.
In the next test suite, we are already querying agentless data. If that suite fails, it should be sufficient to help identify where the problem lies.
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.
I've since removed the health checks and decided to simplify this and only check that we receive findings. If we are receiving findings that should indicate a good health and working Agentless agent.