-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Unskip test for agentless integrations #184308
[Fleet] Unskip test for agentless integrations #184308
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
@elasticmachine merge upstream |
Pinging @elastic/fleet (Team:Fleet) |
if (agentCount !== 0 && !isAgentlessIntegration(packageInfo) && formState !== 'CONFIRM') { | ||
if ( | ||
agentCount !== 0 && | ||
!(isAgentlessIntegration(packageInfo) || isAgentlessPackagePolicy(packagePolicy)) && |
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 noticed that in the previous PR I forgot to add isAgentlessPackagePolicy(packagePolicy)
, fixing it now.
} | ||
if (path === '/api/fleet/agent_download_sources') { | ||
return Promise.resolve({ data: { items: [] } }); | ||
} |
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 was getting an error regarding these endpoint not being mocked.
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.
LGTM 🚀
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
To update your PR or re-run it, just comment with: cc @criamico |
Fixes #184191
Summary
With merge of #183045 some tests related to agentless started failing in main. I realized that there was a missing condition in a form, so this PR adds that condition and fixes the failing test.
Note: the test wasn't flaky, it was failing on each run after merge. For some reason it never failed on the branch, however there was a concurrent merge of another PR that touched the same UI and that could have something to do with it.
Checklist