-
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] add setup technology selector to add integration page #189612
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
/ci |
/ci |
/ci |
@kilfoyle - Could you help with a quick check of the text here 🙏 |
...olicy/create_package_policy_page/single_page_layout/components/setup_technology_selector.tsx
Outdated
Show resolved
Hide resolved
Pinging @elastic/fleet (Team:Fleet) |
...et/sections/agent_policy/details_page/components/package_policies/package_policies_table.tsx
Outdated
Show resolved
Hide resolved
This looks great! I added a couple of small suggestions for the UI text. |
…policy/create_package_policy_page/single_page_layout/components/setup_technology_selector.tsx Co-authored-by: David Kilfoyle <[email protected]>
…policy/details_page/components/package_policies/package_policies_table.tsx Co-authored-by: David Kilfoyle <[email protected]>
Tried to test in kibana pr deployment, but it seems the agentless url is not set there (tried to enable the feature flag, but still the agentless selector is not showing up). |
Agentless is only supported in serverless deployments for now, so ESS deployments won't be able to set up agentless. |
Looks good, I have a comment and a question. I am glad you have not moved the CSP plugin's SetupTechnology selector because we still have some ongoing work with that and we may migrate that later. I also have a PR to add the Beta badge and default the selected value of the SetupTechnology to Agent-based. Are you doing the same? I saw some similar code changes in the setup_technology hook and I thought you were but it was not in the requirements. |
@juliaElastic If you deploy this to one of our Cloud First test environments and you use your @elastic.co account you can bypass the allow-deny list and edit the configurations to enable agentless in ESS |
Yes, made that changes, it's in the description. We can unify the selector component with the one in cspm plugin 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.
LGTM, left just a small comment.
x-pack/plugins/fleet/public/components/package_policy_actions_menu.tsx
Outdated
Show resolved
Hide resolved
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
…on policy (#190391) ## Summary Related to #183863 Follow up from #189934 (comment) Since the edit integration was re-enabled for agentless integration policies, we have to make sure to hide the agent policy change option when editing an agentless policy. This pr addresses that. To verify: - add CSPM integration with agentless setup technology - edit the integration policy - verify that the agent policies can't be modified - upload another agentless package (instruction [here](#189612)) - add Agentless integration with setup technology agentless - edit the integration policly - verify that the agent policies can't be modified <img width="1526" alt="image" src="https://github.com/user-attachments/assets/557cc6d4-37e7-43f6-b52a-3d5f4c073e1c"> <img width="1524" alt="image" src="https://github.com/user-attachments/assets/e890efa8-4faf-4608-9228-32debadb895a"> ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Added back agent monitoring on agentless policies as requested. It was incorrectly removed in #189612
Summary
Closes #183863
TODO refactor cspm integration so that the same setup technology selector is used as other packages
I might do this in a separate pr, it seems this pr also adds Beta badge to the cspm selector #189217
Note: in Serverless, currently the preconfigured
agentless
agent policy is being used for all agentless integrations. When Agentless API is supported in serverless, this code can be removed and serverless will work the same way as ESS. Related issue https://github.com/elastic/security-team/issues/9781Open question:
Requirements completed:
deployment_modes.agentless.enabled: true
is set on a given policy templatesupports_agentless: true
set.supports_agentless: true
is set, the policy editor default to the current agent-based option and the toggle is set toagent-based
agentless
option is clearly marked as beta, and display a beta banner in the policy editor form itself to reiterate this when agentless mode is enabledSteps to verify locally (ESS):
kibana.dev.yml
:Verify Agent-based option:
Agent-based
option selected by defaultVerify Agentless option:
Agentless
option in the selectorNote: locally the agentless API won't work, comment out this line to test https://github.com/elastic/kibana/blob/main/x-pack/plugins/fleet/server/services/agent_policy_create.ts#L178
Checklist